The connection is open for verly long time (>24h), so I thought that
the peer may force a renogatioation due to the session timeout. Or
have I got something wrong and a renogatioation is not necessary for
long-running sessions?
--
openssl-users mailing list
To unsubscribe:
>The code above does what I want - except for renegotiations!
Do you absolutely, positively, HAVE TO support renegotiation?
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi everybody!
I am working on a program where each peer may write at any time, so
the other side has to be able to read incoming data when it gets
available. If the peer sent nothing my program must be able to call
SSL_write() to send its own data to the other side.
My code currently does this
Of course people have been harvesting entropy, or trying to, from network
sources for decades. There's a famous paragraph regarding it in RFC 4086, which
is an expanded version of a similar statement from RFC 1750 (1994):
Other external events, such as network packet arrival times and
find / -type f -exec {} version \;
find / -type f -exec objdump -x {} \;
find / -type f -exec ldd {} \;
looks like you only have 1 openssl binary, 0.9.7.a on your host.
objdump -x & ldd will show you which libraries the openssl binary is compiled
to use on your host.
so….
objdump -x [ full
Here is result for first command:
find / -type f -name openssl
-exec {} version ;
OpenSSL 0.9.7a Feb 19 2003
What means repeat with?
What I have to type for next comand exactly please?
objdump -x &
ldd.
Il 04.06.2018 08:30 FooCrypt ha scritto:
> find / -type f
-name openssl -exec {}
find / -type f -name openssl -exec {} version \;
repeat with
objdump -x & ldd to determine which libraries, etc are being used.
> On 4 Jun 2018, at 3:47 PM, Sampei wrote:
>
> Can you help to understand if I have 2 OPenSSL installed into my "old old"
> server please?
>
> rpm -qa | grep
