Nelson B. Bolyard wrote:
Winston O'Brien wrote:
Folks;
I send an encrypted/signed email to someone. Moz encrypts my copy in
the Sent folder. (I won't start a flame about not giving me a choice.)
Then the email is saved using Save as.. to an external .eml file and
still encrypted.
Now,
All my certs are current and issued by the same CA. The subject is
different, though not by much (basically a firstname.lastname.serial).
The reason I have multiple certs from the same CA is political, and
the older, primary cert has more functionality but I have to keep the
new one for a server
Hello,
The addbuiltin cmd creates a certdata.txt, which is then used to build
the nssckbi lib. A couple of things about that:
1. The new certdata.txt does not get processed properly by
certdata.perl (when doing the gmake generate in
mozilla\security\nss\lib\ckfw\builtins); but got it to work
Winston O'Brien wrote:
Nelson;
I was hoping this wasn't the answer. This says that Moz is a closed
product that doesn't interact with other products even when using RFC
standard protocols and algorithms.
I have started to try the certutil and cmsutil tools. Unfortunately,
I run FreeBSD
POC wrote:
Hello,
The addbuiltin cmd creates a certdata.txt, which is then used to build
the nssckbi lib. A couple of things about that:
1. The new certdata.txt does not get processed properly by
certdata.perl (when doing the gmake generate in
mozilla\security\nss\lib\ckfw\builtins); but got it
Actually, why do you want to create a builtin CA with valid CA trust?
The purpose of the builtin module is to supply trusted roots, which is
probably why valid CA trust was overlooked - we only use the trusted CA bit.
-Ian
Ian McGreer wrote:
POC wrote:
Hello,
The addbuiltin cmd creates a
JSS 3.3 has been released to mozilla.org and
/share/builds/components/jss/JSS_3_3_RTM/.
This latest version of JSS has better support for encryption through the
Java Cryptography Architecture (JCA) interface; support for AES; a new
SecretDecoderRing that supports hardware tokens, multiple
Winston O'Brien wrote:
Nelson;
I was hoping this wasn't the answer. This says that Moz is a closed
product that doesn't interact with other products even when using RFC
standard protocols and algorithms.
No, it says nothing of the sort.
mozilla sends RFC 822 and MIME and SMIME
±z·Q¦¨¬°¤@¦ì±N¨Ó¦~Á~¦Ê¸Uªº¤H¶Ü
¥H¤Uªº¸ê°T±NÅý±zªº¤H¥Í¦³«¤jªºÂàÅÜ
¦pªG±z¤£¬Ý´N¿ù¥¢¤@Ó¤j¦n¨}¾÷¤F
¦pªG¦³¤@Ó¦ÑÁóÄ@·N¤£¦b¥G§Aªº¾Ç¸g¾ú¡A¤W¤U¯Z¥¿¤£¥¿±`¡A¦³µL°^Äm«×¡A³£µ¹§A°_Á~35000¤¸!¨C¦~ÁÙÀ°§A¥[Á~10%!!§A·|±o¨ì¤°»ò¤H¥Í!?
²Ä¤@¦~ 35000 ¡Ñ12 ¡×42 (¦~Á~)²Ä¤G¦~ 42
¡Ñ1.1(¥[Á~10¢M)¡×
Tom,
tom glaab wrote:
All my certs are current and issued by the same CA. The subject is
different, though not by much (basically a firstname.lastname.serial).
The reason I have multiple certs from the same CA is political, and
the older, primary cert has more functionality but I have to keep
10 matches
Mail list logo