-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Melissa,

@01 May 2002, 11:55:30 -0700 (19:55 UK time) Melissa Reese wrote in
[EMAIL PROTECTED]">mid:[EMAIL PROTECTED]

> Please explain this then...

> I'm using 1.60c. All of Lynna's S/MIME signed messages show here as
> "invalid" with *both* TB!'s internal S/MIME implementation and with
> MS CryptoAPI (and yes - her key is properly imported here as well).

Switch to MS Crypto and *then* import the certificate. That may make a
difference. Remember to move off the message and back on again to
re-verify.

> If I "open" her certificate to have a look, it says: "No signed
> attributes".

That sounds like a non-imported certificate. I think the magic formula
is: Use CryptoAPI; Import certificates with CryptoAPI;

You also have to make sure that the CA is in your certificate store.

- --
Cheers -- .\\arck D. Pearlstone -- List moderator
SB! v1.60d/iKey1000-5523848F0B1 on Windows 2000 5.0.2195 Service Pack 2
·
-----BEGIN PGP SIGNATURE-----

iD8DBQE80EAvOeQkq5KdzaARAvWAAKDutRl02wvjA/5h12YM5pfgKPq6eQCg1hYY
A2WGWAhqh9/qGXpvgwXbngA=
=dHxb
-----END PGP SIGNATURE-----



________________________________________________________
Current Ver: 1.60h
FAQ        : http://faq.thebat.dutaint.com 
Unsubscribe: mailto:[EMAIL PROTECTED]
Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]

Reply via email to