Hello,
Thanks a lot for the fix.
Kind regards,
Franck Levionnois.
2014-03-19 18:37 GMT+01:00 Stephen Henson via RT :
> On Wed Mar 19 15:10:17 2014, flevionn...@gmail.com wrote:
> > Hello,
> >
> > After verification, it turns out that the signature wasn't made with
> > bouncy
> > castle. Howeve
Thanks Stephen. I was not aware other implementations used both forms. What
if OpenSSL implemented one of these options:
1) Don't change p12_key.c. Don't change the default behavior of pkcs8.c.
But at least add a command line option to pkcs8.c (-stdemptypw) to be
standard-compliant (make P empty).
On Thu Mar 20 09:09:31 2014, mbev...@google.com wrote:
> The "openssl pkcs8" CLI tool fails to properly decrypt a file containing an
> EncryptedPrivateKeyInfo structure encrypted with an empty password (see
> error below). This happens when a PKCS #12 algorithm is used (such as
> PBE-SHA1-3DES); I
Hello,
Thanks a lot for the fix.
Kind regards,
Franck Levionnois.
2014-03-19 18:37 GMT+01:00 Stephen Henson via RT :
> On Wed Mar 19 15:10:17 2014, flevionn...@gmail.com wrote:
> > Hello,
> >
> > After verification, it turns out that the signature wasn't made with
> > bouncy
> > castle. Howeve
The "openssl pkcs8" CLI tool fails to properly decrypt a file containing an
EncryptedPrivateKeyInfo structure encrypted with an empty password (see
error below). This happens when a PKCS #12 algorithm is used (such as
PBE-SHA1-3DES); I have not investigated PKCS #5 algorithms. I hit this bug
when a
