It’s the passwort which protects the p12 file. If you were given a ‘PIN’ for
your pfx file, try that.
OpenSSL calls it ‘import passwort’, because it is importing from p12 format and
exporting to
pem format.
Two remarks about those three commands:
If you omit the `-nodes` argument in the first
I received a pfx file from one our techs. A pfx file is a cert and key, all
in one binary file. He needs me to split it out into the cert and the key,
so I can create a new request from that key, and then sign a new cert for
him.
(no, I don't know why he can't just create a new request. And I woul
If you generated a keypair in a smartcard, how did you extract the private key
out of it??? The whole point of a smartcard is to prevent that from being
possible.
So, like Ken suggested, I’ve no idea where the private key you posted was
coming from – but reasonably sure it has no relation to
On 2/13/2020 12:40 PM, Pedro Lopes wrote:
When I try to verify the signature, fails
with RSA_padding_check_PKCS1_type_1:invalid padding.
That error typically means that the verification public key does
does not match the signing private key.
Hello,
I'm generating a key pair in a smartcard (as a session object), then I
convert both keys to RSA openssl objects.
Then I save both into different files.
I tried use these keys to sign and verify (private encrypts and public
decrypts).
When I try to verify the signature, fails
with RSA_paddi
> From: Michael Leone [mailto:tur...@mike-leone.com]
> Sent: Wednesday, February 12, 2020 16:09
>
> On Wed, Feb 12, 2020 at 4:19 PM Michael Wojcik
> wrote:
> >
> > the infamous "The OSI of a New Generation" presentation
>
> I'm not sure how "infamous" it is, as I've never heard of it, even in
> pa
