Wednesday, September 4, 2002, 6:23:52 AM, Daniel scribbled: DS> Hi,
DS> 1) I just wanted to know, if this bug is fixed for you: DS> [-] Fixed a bug of Beta/2 with S/MIME internal implementation. It didn't DS> check correctly the signatures. DS> For me, it isn't. DS> If I change the S/MIME engine to 'Microsoft CryptoAPI' all signed mails DS> are checked correctly. DS> If I change it back to the 'internal implementation' most (not all) of DS> the signatures are marked as invalid. Doubleclicking on such an invalid DS> signatures gives me following error: DS> PKCS#7 object cannot be parsed. Failed to verify the message. No DS> signatures information available. DS> Do you have the same behavior with _this_ email ? Valid with 'Microsoft DS> CAPI', INvalid with 'internal implementation'. Watch out, if you test DS> it, after you have changed the S/MIME engine settings (Options - DS> S/MIME), you have to select an other email and then switch back to this DS> one, to activate the new engine settings. DS> 2) Are you able to sign outgoing mails when S/MIME engine is set to DS> 'Microsoft CAPI' ? I'm not. If I switch to 'internal implementation' it DS> works perfectly well. DS> Maybe I'm wrong, but when 'Microsoft CAPI' is selected, I'm not able to DS> 'Edit personal certificates' - so maybe it is not expected to work using DS> 'Microsoft CAPI' ? DS> Greetings Daniel DS> -- DS> Using The Bat! v1.62/Beta5 on Windows 2000 5.0 Build 2195 Service Pack DS> 2 DS> (I know, this email has _not_ been sent using The Bat!, but to DS> demonstrate my problem I had to sign it using my keys stored on iKey) Nope. Didn't work. Mike ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
