OpenSSL::PKey::EC#to_pem or .new appears to change EC keys created by CRuby's openssl #257

Activity

1. kares commented on Apr 11, 2024

   

   kares

   on Apr 11, 2024

   Member

   More actions

   not sure about whether the format is expected to be "byte level" same between C-OpenSSL and Java's Bouncy-Castle...
   as long as one is able to parse other's PEM encoded format and end up with the same object.

   The PEM exported by jruby-openssl appears to be much shorter than the PEM exported by CRuby's openssl.

   was due 401749e which explicitly skipped the public part when encoding the private key
2. jcharaoui commented on Jan 17, 2026

   

   jcharaoui

   on Jan 17, 2026

   More actions

   I think the main problem is that it's not possible to instantiate an OpenSSL::PKey::EC object from the PEM format it generates itself:

   irb(main):002:0> ec = OpenSSL::PKey::EC.generate("prime256v1")
   => #<OpenSSL::PKey::EC:0x21f7e537>
   irb(main):003:0> OpenSSL::PKey::EC.new(ec.to_pem)
   org/jruby/ext/openssl/PKeyEC.java:356:in `initialize': Neither PUB key nor PRIV key:  (OpenSSL::PKey::ECError)
           from org/jruby/RubyClass.java:923:in `new'
           from (irb):3:in `evaluate'
           from org/jruby/RubyKernel.java:1277:in `eval'
           from org/jruby/RubyKernel.java:1725:in `loop'
           from org/jruby/RubyKernel.java:1426:in `catch'
           from org/jruby/RubyKernel.java:1426:in `catch'
           from /usr/bin/jirb:13:in `<main>'
   

   This works without issues with MRI.

   👍React with 👍1Reacted by Carl Winbäck
3. kares

   linked a pull request that will close this issuecompatibility improvements #343on Mar 6, 2026
4. kares

   closed this as completedin #343on Mar 13, 2026