Hi,
when switching RPMs from 0.2.4.x to 0.2.5.x branch I forgot to merge re-enabling of Curve25519 (it was a historic artifact of EL5 workarounds).
RPM packages of 0.2.5.10 with Curve25519 reenabled are now uploaded and should get to you shortly.
Ondrej
Why does this package: send Tor SIGTERM instead of SIGINT (during yum update)? lower "ulimit -n" to 32768?
-Pascal
On 10/27/2014 7:51 AM, Ondrej Mikle wrote:
Hi,
when switching RPMs from 0.2.4.x to 0.2.5.x branch I forgot to merge re-enabling of Curve25519 (it was a historic artifact of EL5 workarounds).
RPM packages of 0.2.5.10 with Curve25519 reenabled are now uploaded and should get to you shortly.
Ondrej _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 10/27/2014 10:54 PM, Pascal wrote:
Why does this package: send Tor SIGTERM instead of SIGINT (during yum update)?
SIGTERM has been used in that script since before I was packaging it, I never changed it.
Ondrej
tor-relays@lists.torproject.org
-
Ondrej Mikle -
Pascal