I am trying to generate a certificate request for an EC key from Firefox
3.0.1 (downloaded from mozilla.org). A pop up (key generation?) appears
briefly but quickly disappears. The Java error console contains the
following message:
Error: uncaught exception: [Exception... "Component returned fa
Some have groused that the ordering of cipher suites has an bias against
FIPS. For example, Camelia and RC4 seem to be prefered over AES. Is the
rationale for the ordering documented or explained somewhere? My guess is
that speed was a consideration.
cipher_suites[34] = {
Teh Chang wrote, On 2008-07-25 12:03:
>> On Fri, Jul 25, 2008 at 6:59 AM, mozilla <[EMAIL PROTECTED]> wrote:
>>> I expected FF3.0.1 to do TLS with the specific ECC ciphersuite that you
>>> identify. However, my FF3 is not offering the ECC suites in its client
>
There is no LD_LIBRARY_PATH defined in the shell environment variable set.
Again, I did not disable anything.
"Wan-Teh Chang" <> wrote in message
news:[EMAIL PROTECTED]
> On Fri, Jul 25, 2008 at 2:49 PM, Nelson B Bolyard <[EMAIL PROTECTED]>
> wrote:
>>
>> I suspect that it MAY be the case that t
> wrote in message
news:[EMAIL PROTECTED]
> On Fri, Jul 25, 2008 at 6:59 AM, mozilla <[EMAIL PROTECTED]> wrote:
>> I expected FF3.0.1 to do TLS with the specific ECC ciphersuite that you
>> identify. However, my FF3 is not offering the ECC suites in its client
>> hello
I expected FF3.0.1 to do TLS with the specific ECC ciphersuite that you
identify. However, my FF3 is not offering the ECC suites in its client
hello. I downloaded FF3.0.1 from the mozilla.com site yesterday (7/24/08). I
just did the quick download without any custom configuration. (There should
I'm trying to do TLS using an ECC ciphersuite. I thought FF3 natively
supported it (ECC ciphersuites are enabled in about:config). Using normal
downloads of FF3 on either Linux or Windows I'm getting the error that
there's no common ciphersuite. Looking at SSLTap, both versions of FF3
browser a
jects/security/pki/nss/nss-3.12/nss-3.12-release-notes.html#docs
http://www.mozilla.org/projects/security/pki/nss/nss-3.11.4/nss-3.11.4-build.html
cvs co -r NSPR_4_7_1_RTM mozilla/nsprpub
cvs co -r NSS_3_12_RTM mozilla/dbm mozilla/security/dbm
cvs co -r NSS_3_12_RTM mozilla/security/coreconf mo
Thanks. Sounds like I the basic version.
"Glen Beasley" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> mozilla wrote:
> > Thanks. That helps. The referenced Java program implies that 192 and
224
> > are recognized values for the kpg initiali
ameterSpec.html
>
> was introduced in J2SE 1.5.
>
> JSS cannot provide ECGenParameterSpec at this time since JSS still has
> to work with J2SE 1.4.2 (so FUN...)
>
> but the current implemenation creates the suite B curves by default.
> Meaning JSS PK11KeyPairGenerator is
> hard coded
I am trying to use JSS for TLS/SSL communciations from inside an application
server; more specifically I am writing a plugin component for an application
that may already use (and initialize) JSS. It is not clear from the Javadoc
how initialization should work in this case.
1) Is it possible t
11 matches
Mail list logo