On 2009-08-20 07:27 PDT, Brendan wrote:
> I am having trouble decoding a custom extension that I created using
> Openssl. I have created the templates for nss but I am receiving a
> "bad der" error number from the decoder. As far as I can tell the der
> is correct and can be parsed by openssl comm
On 2009-08-21 12:39 PDT, Neil wrote:
> Polly wrote:
>
>> Neil wrote:
>>
>>> Polly wrote:
>>>
Tom, you asked what third party DLLs I'm using -- it's the openssl
DLLs ssleay32.dll and libeay32.dll.
>>> One possible alternative might be to rewrite your code to use NSS?
>>>
>> Thank
Polly wrote:
Neil wrote:
Polly wrote:
Tom, you asked what third party DLLs I'm using -- it's the openssl DLLs
ssleay32.dll and libeay32.dll.
One possible alternative might be to rewrite your code to use NSS?
Thanks for the suggestion. As it happens, my requirements were
Hi again Ian,
Yes I can appreciate that there are priorities and you're reluctant to
get into something overly complex. It's probably wise then to drop any
attempt to have the application sort out which is the weaker link and
instead just bubble that information up to the user, so that they can
as
Hello Justin,
On 20/08/2009 17:45, Justin wells wrote:
Hi Ian,
Thanks for your reply! It's very enlightening, and I do agree that in
the real world there are a lot of issues other than the cryptographic
issues. Just to be sure, I am not suggesting that the weakest link
should be as strong as th
5 matches
Mail list logo
