On Mon, Oct 21, 2002 at 02:50:43PM -0700, J wrote:
> Has anyone had trouble with using the OpenSSL library on HP-UX?? I am using version
> 0.9.6d and there seems to be an intermittent problem with the digest encryption, or
>just
> some of the encryption/decryption routines in the OpenSSL toolkit.
Thanks, it works.
Added to [ new_oids ]:
mycustomexension=1.2.3.4.5
entered into [ my_extensions ]
mycustomextension=DER:01:01:FF
used x509_extensions=my_extensions where needed.
(names are dummynames)
Nevertheless, in the certs one only sees the oid. Suppose, that cleartext
will be only availa
Hello Everyone,
Has anyone had trouble with using the OpenSSL library on HP-UX?? I am using version
0.9.6d and there seems to be an intermittent problem with the digest encryption, or
just
some of the encryption/decryption routines in the OpenSSL toolkit. It does not happen
all the time on HP-UX
Title: Message
Hi Rohit,
Did you make any progress with this?
I saw your message on the openssl listserv, and the response.
I’m not familiar with the functions
that you are using, but I’ll try and help if you need it. One suggestion is to use the openssl “asn1parse” command to
On Mon, Oct 21, 2002, Karl-Michael Werzowa wrote:
> Thanks, it works.
>
>
> Added to [ new_oids ]:
> mycustomexension=1.2.3.4.5
> entered into [ my_extensions ]
> mycustomextension=DER:01:01:FF
> used x509_extensions=my_extensions where needed.
> (names are dummynames)
>
> Nevertheless, in the
> pkcs7 structure before sending it to windows client. On windows client we
> are trying to use capicom library to decrypt the data where we are failing.
> I will keep you posted as we make progress. Meanwhile if you got any
> pointers, please do send us.
i haven't looked at encryption, but capi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Version 4.02, 2002.10.21, urgency: HIGH:
* Serious bug in ECONNRESET handling fixed.
Homepage: http://stunnel.mirt.net/
Download: ftp://stunnel.mirt.net/stunnel/
Best regards,
Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
C
Hi,
I know the advice is to use a single SSL context per application.
My situation however is that I'm writing some software that will
accept inbound connections and setup outbound connections as well.
I don't want to be bound by using the same certificates for inbound
and outbound connections. So
Title: Message
Hi,
Thanks to everybody who responded to this mail.
As per
now, we have not made much progress on it. I think openssl understands the
certificate encoding. I was able to decode it usin x509 command. Certificate was
in DER format and we were able to get the output in text for
