2010/1/17 John R Pierce
> Josselin Jacquard wrote:
>
>> Thanks for your response.
>> Let's say A wants to contact B with SSL.
>> A send a ssl request to B, but C instead of B answers, because C and B
>> have the same address (maybe there are behind the same NAT
2010/1/17 Dr. Stephen Henson
> On Sun, Jan 17, 2010, Josselin Jacquard wrote:
>
> > Thanks for your response.
> > Let's say A wants to contact B with SSL.
> > A send a ssl request to B, but C instead of B answers, because C and B
> have
> > the same addres
h? can't be an application layer
> flag?
>
> 2010/1/15 Josselin Jacquard
>
> Hi,
>>
>> I'm wondering if there is a way to pass on external application data
>> during a handshake, without putting it into the x509 cert, because I don't
>> want to
Hi,
I'm wondering if there is a way to pass on external application data during
a handshake, without putting it into the x509 cert, because I don't want to
sign it every time I change the ex data.
I've got multiple server instance running at once on the same adress, and
the client choose to contac
? If true, how can I avoid the sock_write error ?
Thanks in advance
Joss
2009/12/15 Josselin Jacquard
> Hi,
> When I'm connecting to a peer who crashes, I try to close the connection
> with :
>
> if (ssl_connection != NULL)
>
> {
> SSL_shutdown(s
Hi,
When I'm connecting to a peer who crashes, I try to close the connection
with :
if (ssl_connection != NULL)
{
SSL_shutdown(ssl_connection);
}
It crashes on windows, and on linux, with a debugger attached, the program
freezes with this call stack :
0write/lib/lib
Hi all, i'm using openssl on top of a pgp authentication.
I've got a null pointer exception with ctx->current_cert (the other testers
of my project don't have this null pointer) and I don't understand why this
pointer is null.
I've change ctx->current_cert to ctx->cert to make it work. Is it secu
