Dear all
i'm new to openssl i want use it with network simulator NS3 i
just want steps to begin to reuse openssl with a C code to make a
certificate authority entity that create certificate if any one know how
can i begin with this project i need help to finish my master degree
please
--
Thanks, and yes.
A co-worker was having a look at the stunnel code while I was pursuing
this. He found the message in their "verify.c" as well as a bug report
against v4.32. They were checking for the cert's Subject to precisely
match, throwing this error on a mismatch. It was patched in v4.4
On Tue, Aug 19, 2014, Eckert, Doug wrote:
> Greetings.
>
> After a recent reboot, a previously working cert is now being rejected with
> "NO X509_NAME". I can't set the log level higher on the AIX side to get
> more detail. What are the most likely causes of the "NO X509_NAME" error?
>
> from
You might also wish to verify that the openssl binary you're using for
c_rehash is version 1.0.1e.
-Kyle H
On 8/20/2014 7:16 AM, Eckert, Doug wrote:
> The "Verify return code: 19" was because I specified the wrong CApath
> on the s_client.
>
> s_server/s_client works perfect. I also tried s_serv
I'm not sure what WINDOWS means. And I'm not sure MSFT knows either :)
Less flippantly, the goal is that OPENSSL_SYS_WINDOWS means any Windows
platform, and then there are subtypes within that. We'll figure it out as we
go along. It's gonna take a while to clean up the #ifdef world without
b
On Wed, Aug 20, 2014 at 10:12 AM, Salz, Rich wrote:
>> Minor clarification is appropriate. MSDOS is supported in single "stance",
>> namely DJGPP, which is 32-bit environment.
>
> Good point.
>
> So the idea is that MSDOS gets turned into DJGPP. BEOS and OS/2 are removed
> in HEAD (i.e., after 1
The "Verify return code: 19" was because I specified the wrong CApath on
the s_client.
s_server/s_client works perfect. I also tried s_server with the stunnel
client, and the cert is accepted no problem. I think this lies solely with
the stunnel server process.
Thanks so much for the extra set
> Minor clarification is appropriate. MSDOS is supported in single "stance",
> namely DJGPP, which is 32-bit environment.
Good point.
So the idea is that MSDOS gets turned into DJGPP. BEOS and OS/2 are removed in
HEAD (i.e., after 1.0.2), and Microsoft means WINDOWS of various flavors.
If this
It's stunnel 4.32 compiled on AIX 6.1 (TL8 SP3) with openssl 1.0.1e.
Initially I thought this was in OpenSSL due to the "NO X509_NAME" message
in the stunnel log. It had been working fine for years with the same
certs, config files, etc with OpenSSL 0.9.8x and prior. Now I'm not so
sure.
When I
> Does anyone want to speak up for the requirement that we continue to
> support BEOS (apparently B/1 and R5?), OS/2, or pre-Windows MSDOS?
Minor clarification is appropriate. MSDOS is supported in single
"stance", namely DJGPP, which is 32-bit environment. 16-bit code was
never supported by OpenS
10 matches
Mail list logo
