Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:39:36Zhttps://gitlab.torproject.org/legacy/trac/-/issues/13471router daemon crashes with openssl built no_ssl32020-06-13T14:39:36Zstarlightrouter daemon crashes with openssl built no_ssl3Access violation when 'tor' is run with
openssl-1.0.1j built with no_ssl3 option and
openssl s_client -ssl3 -connect x.x.x.x:x
is run against the OR portAccess violation when 'tor' is run with
openssl-1.0.1j built with no_ssl3 option and
openssl s_client -ssl3 -connect x.x.x.x:x
is run against the OR portTor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/13361Using 'undocumented' option accept6 fails2020-06-13T14:39:24ZTracUsing 'undocumented' option accept6 failsI've been working on upgrading my tor-relay to use IPv6
For IPv4 I reject exiting, I'm on a single IP ftth network, exiting from this IP is /bad/ ;)
However since IPv6 is now available in tor exiting on IPv6 would be a good strategy to...I've been working on upgrading my tor-relay to use IPv6
For IPv4 I reject exiting, I'm on a single IP ftth network, exiting from this IP is /bad/ ;)
However since IPv6 is now available in tor exiting on IPv6 would be a good strategy to benefit the network more.
Hence configuration was added:
ORPort [2A02:80C0:FF70:f600::2]:9001
OutboundBindAddress [2a02:80c0:ff70:f600::2]
IPv6Exit 1
ExitPolicy accept6 *:*
ExitPolicy reject *:* # no exits allowed
Adding accept6 does not throw errors, without it atlas shows my node not allowing exiting of IPv6.
However it seems that unfortunately and expectantly accept6 /also/ allows exiting of IPv4
Config-file+build options can be provided if needed, contact me at gijsje+tor [AT] heteigenwijsje [DOT] nl
Running on FreeBSD 10 x64
nodename: heteigenwijsje
**Trac**:
**Username**: gizah