ignature.
There is a separate field (digestEncryptionAlgorithm) indicating
the OID of the signature algorithm. Look at this and see if it is
different from the value in the outer signature, and look up the
value online to see what it means.
On 22/09/2014 10:24, Prasad Dabak wrote:
> Well,
On Sep 19, 2014, at 10:24 AM, Jakob Bohm wrote:
On 19/09/2014 09:14, Prasad Dabak wrote:
> The RFC links helped.
>
> I am able to do decrypt the encrypted digest and match it with the
> DigestInfo as explained in rfc2315.
> DigestI
check this behavior? If
the size of decrypted counterSignature is equal to size of the hash, assume
that digestAlgorithm field is not considered?
Thanks.
-Prasad
On Sep 16, 2014, at 10:51 AM, Jakob Bohm wrote:
On 16/09/2014 12:22, Prasad Dabak wrote:
> Hello,
>
is doesn't look like a SHA1 hash like in case (1) and (2). So
what type of hash it is? Can someone elaborate OR point to documentation that
elaborates on this?
Thanks.
-Prasad
On Sep 09, 2014, at 10:18 AM, Prasad Dabak wrote:
Thanks Jacob for your response. Very informative indeed!
Thanks Jacob for your response. Very informative indeed!
Thanks
-Prasad
Sent from my iPhone
> On 09-Sep-2014, at 10:05 pm, Jakob Bohm wrote:
>
>> On 09/09/2014 09:01, Prasad Dabak wrote:
>> Thanks Jacob for an elaborate answer. Somehow I never received your response
>>
l
need to update it when I switch to a newer public key?
Thanks.
-Prasad
On Sep 06, 2014, at 09:44 PM, Prasad Dabak wrote:
Hello,
Given a signed Windows portable executable, I want to programmatically verify
two things using openssl APIs
1. Verify the digital signature.
2. Confirm that the exe
Hello,
Given a signed Windows portable executable, I want to programmatically verify
two things using openssl APIs
1. Verify the digital signature.
2. Confirm that the executable is signed by a specific company using that
company's public key.
It seems that part (1) can be done by parsing th
