RE: Outlook Express can't recognize my encrypted mail?
"Colestock, Robert" <[email protected]> Tue, 26 Jun 2001 10:13:17 -0400
| Newsgroups | gmane.ietf.sfl |
|---|---|
| Message-ID | <[email protected]> |
Tuzi: Without digging very deeply into your particular configuration details here, I can only assume that MS Outlook does not like the public key in your certificate. I have found integration with Outlook touchy; everything must be aligned just perfectly (especially certificates). It sounds like you have resolved most issues, please check the public key in the certificate (what exactly is the error from MS Outlook?). Check that you have a certificate with an RSA key that looks like the RSA certificate that works (bit length, OID and size of the public key). Also, what version of Outlook; my integration was with the older MS Outlook Express 97. The certificate of interest should have been exported from MS Outlook in order for the SFL logic to build an encrypted key. Please check that the SFL recipient key file matches the public key details in the MS Outlook for your particular login (i.e. you must login to the user, e-mail DN matching, that matches the private key of the SFL specified recipient certificate). All DNs/e-mail addresses must match! This is not easy; I always have to generate new private key/certificate pairs when I test since my internal MS Outlook e-mail address keeps changing (between integration tests). You should be able to see this easily by looking at what internal choices you have to perform encryption operations, this certificate should match the SFL specified Recipient certificate file. If you still have problems, I will try and get to this investigation next week. Bob Colestock VDA. -----Original Message----- From: tuzi [mailto:[email protected]] Sent: Tuesday, June 26, 2001 1:24 AM To: [email protected] Subject: Outlook Express can't recognize my encrypted mail? hi all, I encounter some probelm when I try to generate a encrypted mail. I use the tool "mimetest" to do the job. You can see the .cfg files that I use at the end of this mail. All the necessary cer files and data files are put in the subdir ./tuzi. By running "mimetest mimetest.cfg", I can generate a eml file named ./tuzi/tuziEncrypted.eml. I tested this file with a small tool written by SFL (I wrote it myself). This mail can be decrypted correctly. But when I try to read it with Outlook Express (OE), it failed. So I generated another encrypted mail by OE, which can also be decrypted by my tool. It is obvious that my small tool works well. And I am sure that I have imported the corresponding certificates into OE, and this is not due to the dos2unix/unix2dos file format problem (all my programs run on a solaris). So, how to generate a OE compatible encrypted mail with SFL? Thanks all, I really appericiate your help. mimetest.cfg: [hilevel test] verify=1 ## verify flag for test result verification of input output=1 ## -1=no output, 0=pass/fail, 1=all output number_of_runs=1 Logins=./tuziLogins.cfg hi_tests=auto_hi [auto_hi] Smime_EncodeEncrypt ./tuzi/encryptSMIME.cfg ./tuzi/tuziEncrypted.eml #End of mimetest.cfg tuziLogins.cfg: [Logins] Description=Logins for this execution! Login1=tuzi Login2=DLL_NULL [tuzi] LoginType=DLLLogin BuildArgs=sm_free3DLL ./tuzi/tuzi.pfx 123456 DLLFile=libsm_free3DLL [DLL_NULL] LoginType=DLLLogin BuildArgs=sm_free3DLL NULL NULL NULL sm_FREE3 DLLFile=../lib/libsm_free3DLL #end of tuziLogins.cfg ./tuzi/encryptSMIME.cfg: [EnvelopedDataTest] Login1=O=VeriSign, Inc.@OU=VeriSign Trust Network@OU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)98@OU=Persona Not Validated@OU=Digital ID Class 1 - Microsoft@[email protected][email protected] contentFILE=./tuzi/content.in ContentInBuffer=1 ContentOID=1.2.840.113549.1.7.1 ContentEncryptionOID=1.2.840.113549.3.2 # RC2-CBC, OLD definition for MSOE Compatability. Recipient1=./tuzi/tuzi.cer RecipientAddressBook=./comb_ab.dat [email protected] [email protected] IncludeOrigCertsFlag=0 EncodedEnvelopedDataFILE=./tuzi/encryptSMIME.out #end of ./tuzi/encryptSMIME.cfg sincerely tuzi [email protected]