ksreedha...@gmail.com wrote:
On Apr 24, 10:03 am, Wan-Teh Chang wrote:
On Thu, Apr 23, 2009 at 1:51 PM, wrote:
Hello,
I am using Mozilla JSS provider from Java.
JSS 4.2.5
NSS 3.11.4
NSPR 4.6.4
When the FIPS RNG continuous tests fail, what is the behavior in NSS/
Andriy Zakharchuk wrote, On 2009-04-24 02:39:
>>> <0> AAA-update-key
>>> <1> BBB-update-key
>>> <2> CCC-update-key
>> It that literally what you see? Or do you see output with some long
>> strings of hexadecimal characters, e.g.
>> <0> 0549d7e3a1b3c5d7f89 [...]
> Yes, I see symbolic names, no
ksreedha...@gmail.com wrote, On 2009-04-24 14:04:
> Hello,
>
> I am using NSS 3.11.4 and NSPR 4.6.4
>
> Will the non-approved PRNG of NSS be functional/usable when NSS is in
> FIPS mode.
What "non-approved PRNG of NSS" ?
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https:/
On Apr 24, 10:03 am, Wan-Teh Chang wrote:
> On Thu, Apr 23, 2009 at 1:51 PM, wrote:
> > Hello,
>
> > I am using Mozilla JSS provider from Java.
>
> > JSS 4.2.5
> > NSS 3.11.4
> > NSPR 4.6.4
>
> > When the FIPS RNG continuous tests fail, what is the behavior in NSS/
> > JSS. What does it return.
Hello,
I am using NSS 3.11.4 and NSPR 4.6.4
Will the non-approved PRNG of NSS be functional/usable when NSS is in
FIPS mode.
Thanks,
Sreedhar
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
On Thu, Apr 23, 2009 at 1:51 PM, wrote:
> Hello,
>
> I am using Mozilla JSS provider from Java.
>
> JSS 4.2.5
> NSS 3.11.4
> NSPR 4.6.4
>
> When the FIPS RNG continuous tests fail, what is the behavior in NSS/
> JSS. What does it return. do we get an java exception to the calling
> function.
>
>
Right, this seems to work very well. I consider it solved.
Here is the corrected code:
hash: function(str,method) {
var converter = Components.classes["@mozilla.org/intl/
scriptableunicodeconverter"].createInstance
(Components.interfaces.nsIScriptableUnicodeConverter);
converter
The NSS team is pleased to announce the NSS 3.12.3 release.
Please read the NSS 3.12.3 release notes at:
http://www.mozilla.org/projects/security/pki/nss/nss-3.12.3/nss-3.12.3-release-notes.html
Christophe Ravel
NSS Release Engineer
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.o
While it may be technically feasible, Jean-Marc, it would create a
lot of confusion for users, developers and system administrators to
see a P12 file on their file-system that would not have a digital
certificate in it.
I suspect this is the primary reason why the PKCS specs have a #8
specificati
On Apr 23, 3:39 pm, Jean-Marc Desperrier wrote:
> Nelson B Bolyard wrote:
> > Is that python code? I thought it was JavaScript.
>
> Yes, you're right, I had a really too quick look at it :-)
On a second thought, I just had a look at this page:
https://developer.mozilla.org/En/NsICryptoHash
Where
Arshad Noor wrote:
The reason we use the PKCS#8 format is only because, in the multi-step
process of generating a key-pair, creating a CSR and getting a digital
certificate from an internal/external CA, the private-key needs to be
temporarily stored securely until a CA issues the digital certific
Hello Nelson,
thank you for so detailed answer. Please see my comments/answers below.
I have a keys database file (key3.db) and need to export a private key
from it, but can not do this.
What version of the NSS utilities are you using? version 3.??.??
I believe I use version 3.11, however I
12 matches
Mail list logo
