🚀 go-pugleaf

<FONT face=Arial size=2>Hello 
community,<BR><BR>I hope you can help me with the following 
problem.<BR><BR>Basically I receive my bank statements as certificate encrypted 
PDFs. To read them I just place my ATM Card (SECCOS based) into my card reader, 
click on the PDF and it opens fine. That is with Adobe Reader 6.<BR><BR>As soon 
I try to do the same with Adobe Reader 7 I have the following problem. I can see 
the reader accessing the card but still get the error that it cannot decrypt the 
PDF.<BR><BR>This problem drove me crazy so I did some research.<BR><BR>The bank 
told me that they encrypt the statements with the Aloaha Crypto API (<A 
href="http://www.aloaha.com/software-development/c-crypto-sample.php">http://www.aloaha.com/software-development/c-crypto-sample.php</A>). 
<BR><BR>After I got that information I contacted Aloaha in Germany. They told me 
the following (can be read in german on 
http://www.aloaha.com/forum/adobe-7-cannot-use-smartcards-for-de-cryption-%28german%29-t77.html)<BR><BR>Adobe 
Reader 6 uses the windows API wincrypt to decrypt the document. That means that 
the encrypted data is send via CSP to the card to be decrypted. <BR><BR>Adobe 
Reader 7 changed that behavior and uses PLAINTEXTKEYBLOB to get the private key 
of the card. Of course cards are designed that the private key CANNOT be read so 
Adobe Reader 7 fails. It is furthermore very strange that Adobe changed that API 
since CSPs should not allow at all&nbsp; PLAINTEXTKEYBLOB. Microsoft states in 
<A 
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnscard/html/smartcardcspcook.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnscard/html/smartcardcspcook.asp</A>&nbsp; 
that PLAINTEXTKEYBLOB MUST NOT BE USED AT ALL!<BR><BR>So what is now the issue. 
Is this a bug in Adobe 7 that they changed the API not taking smart cards in 
consideration or do they have a reason to exclude smart card usage from their 
software?<BR><BR>Kind Regards<BR>MM</FONT>