Re: [openssl-users] engine interface for genrsa

Hello dear, I joined these group so that l can get assistance for my research work. Up till now, l have not been able. Here is my problem. My Project is an Msc Research on HTTPS Man-In-The-Middle (MITM) Attack using a Compromised Certificate Authority. Now I am going to be very elaborative so

Re: [openssl-users] gpgsm/cms: int_rsa_verify:wrong signature length

Yeah, you're probably right. I was distracted, should have looked closer. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] gpgsm/cms: int_rsa_verify:wrong signature length

> On Apr 23, 2018, at 7:44 PM, Salz, Rich via openssl-users > wrote: > > Your key starts with EF... Since that has the high-bit on, it should be > encoded with a leading zero. Are you sure? That does not look like a key to me... More likely to be the signature

Re: [openssl-users] gpgsm/cms: int_rsa_verify:wrong signature length

Your key starts with EF... Since that has the high-bit on, it should be encoded with a leading zero. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] gpgsm/cms: int_rsa_verify:wrong signature length

Hi, I am using GnuPG to sign 'swupdate' update images, that are verified on the target using openssl: gpgsm -o sw-description.sig -sb sw-description swupdate links against the openssl, but the equivalent cmd line is: openssl cms -verify -in sw-description.sig -inform DER -content

Re: [openssl-users] engine interface for genrsa

On Thu, Apr 19, 2018 at 7:45 PM, Scott Wisniewski wrote: > FYI: > > If you provide an genrsa implementation in your engine that doesn't include > the private parameters, even if it's marked with RSA_FLAG_EXT_PKEY, the > openssl executable will not handle it correctly.