This message: 21/02/2002 10:00 GMT. Hello Marck,
A reminder of what Marck ([EMAIL PROTECTED]) typed on:
21 February 2002 at 09:34:19 GMT +0000
MDP> I did / have and Tony's signatures are still invalid when using MS
MDP> CryptoAPI but valid using internal. Why?
Good question!
The way I see it is, if my signature is valid, which it is, then it
should show that way regardless of anything the recipient does or needs
to do. I thought that was the whole idea of a digital signature
My Certificate is provided by Verisign to BT and then to me. I could
understand these problems if I had a certificate supplied by some less
well know authority but not one originating from Verisign themselves.
I'm getting a bit concerned about this now. I've tried OE and all
signature show as valid without importing or doing anything extra other
than receiving the mail. I even installed Eudora to see what happened.
Both mine and other signatures from other list members show as valid,
again without any additional fiddling.
In all sincerity I don't see how it can be rectified my end of if it's
even my problem at all?
What happens if a digitally signed mail IS tampered with on route and
shows invalid? Do we all tinker, fiddle and faf about with it until we
find a way of showing it as valid? If that be the case then why bother
with a digisig at all?
--
Best regards, Tony. [EMAIL PROTECTED]
Using The Bat! 1.54 Beta/41 S/N A27A5E65
Windows XP Pro 5.1 Build 2600
P4 1.7Ghz
smime.p7s
Description: S/MIME Cryptographic Signature
