Generally openssl security fixes do not
change API/ABIs. In this case I built
the newer release without export ciphers,
thought that seems an unlikely cause.
Perhaps it was memory corruption.
Relay is running on non-ECC CPU,
though the system has never exhibited
any problems related to memory
cor
PS :
I think a defective network equipment could also be the cause of such data
corruptions on incoming data ? May be it should be added on the check list !
But if it's the case, it should be the case for every kind of connexion (try to
download an unzip some big file, just to be sure ;)
Hi,
Very strange !
Data have been corrupted (even the hour), but it seems to be repeated and
constant.
>From my experiences, every "newer library" contains the "older library"
>functionalities (even if improved), it's supposed to be the goal of a library.
>Can somebody confirm that about Ope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My guess is, that the router has a public web interface, listening on
port 443, to the whole world.
Or, your provider blocks port 443, because it doesn't want you to host
your own webserver.
On 04/06/2015 01:15 AM, teor wrote:
>> Date: Sun, 05 Apr
