On Fri, Mar 20, 2009 at 10:49 PM, wrote:
> On Mar 20, 9:59 pm, ksreedha...@gmail.com wrote:
>> Hello,
>>
>> I am using JSS 4.2.5, NSS 3.11.4 and NSPR 4.6.4
>>
>> Many times, my Java Server crashes with the following error.
>>
>> Assertion failure: 0 == rv, at ../../../../../nsprpub/pr/src/pthread
hello,
I created https://bugzilla.mozilla.org/show_bug.cgi?id=487325
for an immediate work around you can choose to use JSS's own SSL
classes, instead
of the JSSE.
-glen
ksreedha...@gmail.com wrote:
Hello Glen,
I tried to look into the source of classes where these exceptions were
thrown.
Sreedhar,
errno would be in your libc. Probably /usr/lib/libc.so or somethnig like
that .
rv is in libnspr4.so . But you need to be in the right frame and in the
right thread in the debugger in order to be able to print it .
Is your version of gdb handling threads properly ? I wonder because
Hello Julien,
When I tried to print the values for rv and errno, gdb complained
saying No symbol for these variables in current context.
I used symbol-file command with all the nspr libraries. and then ran
the command core with the core file.
Which library has these variables.
What I did is,
(
On 04/07/2009 05:38 PM, Jean-Marc Desperrier:
Eddy Nigg wrote:
Adding parameters which adds additional control such a policies and
forcing of smart cards (storage device) would be extremely helpful, once
you get to add some features.
No, the keygen tag is just too bad to be updated to somethin
Eddy Nigg wrote:
Adding parameters which adds additional control such a policies and
forcing of smart cards (storage device) would be extremely helpful, once
you get to add some features.
No, the keygen tag is just too bad to be updated to something really useful.
crypto.generateCRMFRequest is
On 04/07/2009 06:37 AM, Ian Hickson:
Among glaring omissions I would include:
- No support for PINs and associated policies
- No support for TPMs
- No support for key management
I haven't added any new features to at this time. I want to start
by making sure the spec as written matches re
On Tue, 07 Apr 2009 09:34:44 +0200, Ian Hickson wrote:
On Tue, 7 Apr 2009, James Ide wrote:
Going one step further, if the element does support multiple
algorithms, would it be worthwhile to allow it to contain parameters,
e.g. ? On one hand, the set of
widely-implemented algorithms seems smal
On Tue, 7 Apr 2009, James Ide wrote:
>
> Going one step further, if the element does support multiple
> algorithms, would it be worthwhile to allow it to contain parameters,
> e.g. ? On one hand, the set of
> widely-implemented algorithms seems small and fixing attribute names
> like dsaparam
9 matches
Mail list logo
