-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Mcnay, [SM] wrote:
SM> It's a standard Oberthur smartcard. I'm using a SCM Microsystems SM> SCR301 smartcard reader, USB version. The card does not allow SM> exporting of keys. So this would imply that you have to use MS CryptoAPI to use S/MIME in TB! with that key, and you'll also have to test with others using their S/MIME key/s. For encryption, TB! will use the recipient keys in the address book. Also, when using MS CryptoAPI, only those messages signed using that API will appear valid. S/MIME signatures generated using the internal S/MIME will not .... at least this was so the last time I checked. - -- -= allie_M =- | List Moderator PGPKeys: http://www.ac-martin.com/pgpkeys.html _ -----BEGIN PGP SIGNATURE----- Version: PGP SDK 3.0.2 iQA/AwUBP0gYK1fJ62ArBxfiEQJAmwCgzhUvRw5ZKOcDWImrkfkAaUB6tN0AnA2r 7zz6DrMeIvJlStBgePuvqvPn =imF7 -----END PGP SIGNATURE----- ________________________________________________________ http://www.silverstones.com/thebat/TBUDLInfo.html
