Re: request for comments on the crypto.signText functionality
It would be very useful to have the possibility to have the signText() for backward compatibilty with Netscape 4, and have several other function that sign HTML Form Elements. Very important will be the possibility to sign INPUT type=text INPUT type=file, and also radio buttons, and lists. Signing of a file input element would be crucial to an application that we are developing right now. I think that backward compatibility of signText() would be good, but it will not be much important, as currently WEB developers need to code different things for signing HTML in MSIE. It would be a good idea to have a function i.e. signElement() which would sign the contents of a DOM Element. This would make form signing much easier for coders. Regards, Mihail Daskalov Stephane Saux wrote: The Netscape Crypto team is thinking about restoring the 4.X form signing functionality in the next release. We would like to hear from the crypto community, particularly from users of the 4.x crypto.signText() functionality: - Are you happy with the functionality? - If form signing was re-introduced, would signText() backward compatibility be important? - What other form signing features should the Netscape support? Stephane Saux. Manager, Netscape Client Crypto engineering.
Re: Why doesn't SSL SMTP 465 port work with Netscape Messenger?
Michel, Michel Dupagne wrote: Hi! I would like to know why SSL SMTP 465 does not work with Netscape Messenger, at least 4.8 and 7.0. 465 works fine with Outlook Express 4, 5, and 6. I hope you realize that saying SSL SMTP does not work is not nearly enough information to diagnose your problem; That said, the SSL SMTP works fine here. Your problem is most likely of a misconfiguration of your Netscape browsers. Make sure you have the proper ciphers configured that match the ones setup on your SSL SMTP server. Also make sure thqt you have the proper CA certs trusted in the browser.
Re: about NSS
pingzhenyu wrote: How can I buill Nss with VC++,and how can I debug it with VC++ By following the build instructions at http://www.mozilla.org/projects/security/pki/nss/buildnss_33.html .
RE: US Export compliance
Some of the links shown on that page are dead! SSL 3.0: http://www.mozilla.org/projects/security/pki/nss/ssl/draft302.txt SSL connections: http://www.mozilla.org/projects/security/pki/nss/ssl/traces/index.html Client details: http://www.mozilla.org/projects/security/pki/nss/ssl/traces/trc-clnt-ex.html These all fail. Can I find this information somewhere else? Thanks Nick -Original Message- From: Wan-Teh Chang [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 17 September 2002 1:52 To: [EMAIL PROTECTED] Subject: Re: US Export compliance Nick Blievers wrote: Hi, Yes, found that, and that answers some of my questions, thanks. However, the questionairre goes further, asking things such as: -Describe any pre-processing methods -Describe any post-processing methods -Descibe the encryption-related APIs that are implemented and/or supported. Explain which interfaces are for internal and/or external use. -State how the product is written to preclude user modication of the encryption algorithms, key management and key space. -If applicable, explain how the product is the functional equivalent to other encryption software. At the top of the web page I cited is the CCATS number that we received for NSS, the crypto libraries used by Mozilla. You need to work with your legal department to fill out this questionaire. Wan-Teh
