February 2016 - tor-relays - lists.torproject.org

CVE-2015-7547
by starlight.2016q1＠binnacle.cx 17 Feb '16

17 Feb '16

Could someone with a solid understanding of how the Tor daemon interacts with DNS comment on whether and how CVE-2015-7547 (glibc DNS response buffer overflow, remotely exploitable) the bug impacts relay running under Linux?

3 2

Relays with misconfigured MyFamily (declared vs. effective)
by nusenu 17 Feb '16

17 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, the following relays have misconfigured MyFamily settings. 'misconfigured' is defined by declared family does not match effective family (as computed by onionoo's new effectiv_family field [1] - thanks Karsten). Maybe we will see future versions of globe or atlas displaying a diff of the two family sets to make such misconfigurations more visible. Please let me know if you find any errors (I did not fact check the output). +------------------------------------------+----------+ | Contact (truncated) | Fingerpr | +------------------------------------------+----------+ | +1 303-265-9283, rdump@OFTC | 09683D5D | | 0x3AEE83BB539036CA <bb AT symvaro DOT co | 6FDF2D3B | | 0x6F6D60C1 Security Dept <hello@brasshor | 445F1C85 | | 0x6F6D60C1 Security Dept <hello@brasshor | 6BC82EBA | | 0x6F6D60C1 Security Dept <hello@brasshor | 254EB51B | | 0x6F6D60C1 Security Dept <hello@brasshor | B3515F16 | | 0xDE731050 Gareth Llewellyn <gareth@netw | 5CAECF26 | | 0xFD78BCE1 Fruity Oaty Tor Exit <torexit | 1ECD73B9 | | 1024D/1DFBA164 Bernhard M. Wiedemann <to | 172DC95F | | 1024D/39B9820C admin at perfect minus pr | B897826E | | 1024D/39B9820C admin at perfect minus pr | 5FCC8306 | | 1024D/39B9820C admin at perfect minus pr | 2421E10D | | 1024D/39B9820C admin at perfect minus pr | AC7AE98C | | 1024D/39B9820C admin at perfect minus pr | E8B7D19C | | 1024D/39B9820C admin at perfect minus pr | ED9F582E | | 1024D/39B9820C admin at perfect minus pr | B1843B40 | | 1MTUwHFknUyUgRYqpNDYiA2j7sXTYoCe2P | E799227D | | 4096R/8BA2371C Fabian Keil <fk@fabiankei | 34A5FBA4 | | 8192R/0xB431B67770E4AA38 Mikal Villa <me | FE305F8E | | <hneal AT imalazybastard dot com> | CF9E4605 | | <hneal AT imalazybastard dot com> | D12F66D6 | | <periplanetaamericanus AT gmail dot com> | 5B5213C4 | | <periplanetaamericanus AT gmail dot com> | 47D04EC4 | | <periplanetaamericnaus AT gmail dot com> | F19106D7 | | <support at gkware dot com> | E754AA99 | | <support at gkware dot com> | 868A253C | | <support AT gkware dot com> | 48674035 | | <tech AT dana dot io> - 1AgYtavutLAMxUYM | 752DA4A4 | | <tor .AT. jgjtech .DOT. com> BTC: 1QHXLy | 0DA71D95 | | <tor .AT. jgjtech .DOT. com> BTC: 1QHXLy | 31A40828 | | <tor AT 1d4 dot us> - 1N7sBLKvekRD4EUL2b | F1107CB0 | | Abuse Department <abuse AT hartvoorinter | 81B75D53 | | Abuse Department <abuse AT hartvoorinter | 89E3170B | | abuse<__aT>icetor{_DoT===}is - 1GDerBXAJ | 1D9D1C1D | | anders.io | 91361C96 | | anders.io | D56AA4A1 | | anders.io | 3A2192F5 | | Bauruine <torcontact aatt tuxli.ch> - 1C | 63C1904F | | Bauruine <torcontact aatt tuxli.ch> - 1C | 52F7C67B | | BFC62AD3 johannes <tor (@) kontrollappar | 750941D5 | | Big Jim Slade <sysop AT bigjimslade dot | 9AFA555B | | Big Jim Slade <sysop AT bigjimslade dot | ACDC9C49 | | DFRI <tor AT dfri dot se> | A10C4F66 | | DFRI <tor AT dfri dot se> | DD8BD730 | | DFRI <tor AT dfri dot se> | EC84E232 | | DFRI <tor AT dfri dot se> | A478E421 | | Fabian Keil <fk(a)fabiankeil.de> 8BA2371C | 5CE3AD8A | | General Zod <zod(a)kdf.mil> | 556D59FA | | General Zod <zod(a)kdf.mil> | CBABC09D | | GetReal <x50 AT riseup dot net> | 51529D02 | | http://www.onion.network/ <info at onion | F89A5238 | | http://www.privacyfoundation.ch/abuse/ | DC41244B | | http://www.privacyfoundation.ch/abuse/ | 0111BA9B | | http://www.privacyfoundation.ch/abuse/ | DE7DE889 | | http://www.privacyfoundation.ch/abuse/ | 487092BA | | http://www.privacyfoundation.ch/abuse/ | AD86CD1A | | http://www.privacyfoundation.ch/abuse/ | 95DA61AE | | http://www.privacyfoundation.ch/abuse/ | B060482C | | http://www.privacyfoundation.ch/abuse/ | 88487BDD | | https://www.torservers.net/donate.html < | 4E021F36 | | https://www.torservers.net/donate.html < | F657ACB3 | | https://www.torservers.net/donate.html < | 64D500C4 | | iggs <tor.20.iggs AT spamgourmet dot com | 2F557D48 | | jvictors at jessevictors com, PGP 0xC20B | C6DC982A | | jvictors at jessevictors com, PGP 0xC20B | 4B8C39A5 | | jvictors at jessevictors com, PGP 0xC20B | BFA0E9F3 | | jvictors at jessevictors com, PGP 0xC20B | 40DF7E2E | | Kevin <tor AT kberanek dot com> - 14BTbA | 92EA887F | | Kevin <tor AT kberanek dot com> - 14BTbA | A1E02458 | | kingbiskit(a)gmail.com - 18gEJokSQ3uwo3QTM | C921704A | | kingbiskit(a)gmail.com - 1CoXRRwDt6YVTZmJ3 | 3246AF7B | | M.K. Nitrox <mk DOT reg AT t-online DOT | BD912646 | | montanisemperliberi <a> safe-mail.net | E8B6E46B | | Nicholas Merrill <nick AT calyx dot com> | 51BFE90C | | Nicholas Merrill <nick AT calyx dot com> | 0B5E5E70 | | Nicholas Merrill <nick AT calyx dot com> | 84D361B7 | | Nicholas Merrill <nick AT calyx dot com> | E4D1F25D | | Pascal666 at Users dot SourceForge dot N | C9437269 | | Pascal666 at Users dot SourceForge dot N | 5B7AEB14 | | Peter Palfrader | 847B1F85 | | R P <edschlonz AT yahoo dot de> | FF06E7A0 | | Samuel Whited 0x54083AE104EA7AD3 <sam AT | CA54C9F2 | | Sebastian <tor(a)sebastianhahn.net> - 12Nb | EBE718E1 | | snIP3r <sniper(a)restricted-area.de> | 3EE8D536 | | tor TA fejk tod se | 2AFE9201 | | torelay [ANTISPAM at] ruggedinbox [ANTIS | 0559A3D3 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | BAACCB29 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 0B454C7E | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 5A551BF2 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 4436A57F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6D3A3ED5 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 75C4495F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6A29FD8C | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 0C77421C | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 8073670F | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | B35C5739 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | E6E18151 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 6A37488D | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | E11B6AE1 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2 | 70C55A11 | | Torservers.net <support .AT. torservers | 488239E0 | | Torservers.net <support .AT. torservers | 6B1E0019 | | Torservers.net <support .AT. torservers | C46524E5 | | Torservers.net <support .AT. torservers | 770BE0CD | | Torservers.net <support .AT. torservers | 5C84C359 | | Torservers.net <support .AT. torservers | 20B0038D | | Torservers.net <support .AT. torservers | 5714542D | | Torservers.net <support .AT. torservers | B4F883DB | | Torservers.net <support .AT. torservers | 78213EC8 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 4E918B21 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A494237E | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 35FEEA5F | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 2576BFB0 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A1025D32 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | C8D44E91 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | B7EC0C02 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | FFD6C2CE | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 4C6F66B1 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 43D0AB1B | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | A57B43E1 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 9030DCF4 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 3A5F08D0 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 5C1E076A | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 482A381B | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 2D671A4A | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 66CFF345 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 55F5CF9D | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | FEF59210 | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | B4A553CB | | TvdW <tor AT tvdw DOT eu> - bitcoin 1NKK | 92506510 | +------------------------------------------+----------+ ..based on onionoo.thecthulhu.com's data from 2015-07-15 18:00 [1] https://trac.torproject.org/projects/tor/ticket/16276 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVprfXAAoJEFv7XvVCELh0/FcP/28/dhefuPNQaBNSY59NTZTs snwb9vRlAzhDDm0XmWEMIaawFlNjV8shJD8dWvzSvynWHYQySfrStmDdfkpe5CSC lu9ceE6qhhZe+RkyDPM3PdxLhz29XVK+KvQcDcCeWp6nIHzXIOJL+Xk7v7FoU75S Vx8GjhVQd/aiHJQg96zlpdzkAsU000jG2E3Z2EH+gd4Uypl94wgqd0482LSSehiQ LVbhPt6C8NlX32kZ4yAD3W5cHRoyhg30x076X8XHZ16H6F2l801hhON5X32VmXdv vd/kJ7R9JKo4Uig1Y9hq3qpsRsO8aJaN2JOXMsGw2A+6eNFA2OPFLg3/sNKLgiLV N/CPqDlMVsotMDcXX4iBYSHW0Y+J7vyc5ezxE/rKWzBCBZSnK9Sb5UzcrDnOfJRO ABFv+ZtGxSQYVPcnICVdMr+3Kuk0FnKMm7z2ufYriRxDK573LQgNJQnjZ3Tc3JG+ PIVZun0IN/+1gZmQif57xIjW1OFDbDYbhMtYFYbK9zRd7PidIr5NHcYCkEY4whfP 2vhN4jbtYQZZY/hDAMLZVBKDJ42tOYG/8EaWZeMJ8y/pd+F8EvT7ceWzXwuhYm77 WiK4VsgFU7PR7ETi/DJL+ajmFEjpRJ8QOy3J5E/dq/eumkkzL/eBTPL7ydnTmD/u 9271J4DjQYPfjzVtVqdl =ecVW -----END PGP SIGNATURE-----

2 3

Re: [tor-relays] TOR service wont start with ORPort enabled
by Volker Mink 16 Feb '16

16 Feb '16

Hi ! Nope, that was my first idea. No old TOR process running. Best, volker > On 15 Feb 2016, at 00:10, Volker Mink <volker.mink(a)gmx.de> wrote: > > I think I found something..... > >>> could not bind to 0.0.0.0:9001: address already in use > > Where can i set the binding? Is your old Tor process still running? Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

2 1

Re: [tor-relays] TOR service wont start with ORPort enabled (SuperSluether)
by Volker Mink 15 Feb '16

15 Feb '16

Hi! This command brings no output. So no Port 9001 in use... Message: 3 Date: Sun, 14 Feb 2016 07:48:07 -0600 From: SuperSluether <supersluether(a)gmail.com> To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] TOR service wont start with ORPort enabled Message-ID: <56C08597.10905(a)gmail.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Try running "sudo lsof -i :9001" That should tell you what process is bound to the port, and also give you the PID so you can kill it. ***************************

1 0

Re: [tor-relays] TOR service wont start with ORPort enabled
by Volker Mink 14 Feb '16

14 Feb '16

I think I found something..... >> could not bind to 0.0.0.0:9001: address already in use Where can i set the binding? Feb 14 14:04:59 raspberrypi tor[499]: Starting tor daemon...Feb 14 14:04:59.318 [warn] Could not bind to 0.0.0.0:9001: Address already in use. Is Tor already running? Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.324 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 14 14:04:59 raspberrypi systemd[1]: tor.service: control process exited, code=exited status=1 Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.328 [err] Reading config failed--see warnings above. Feb 14 14:04:59 raspberrypi tor[499]: failed. Feb 14 14:04:59 raspberrypi systemd[1]: Failed to start LSB: Starts The Onion Router daemon processes. Feb 14 14:04:59 raspberrypi systemd[1]: Unit tor.service entered failed state. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Multi-User System. Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Multi-User System. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Graphical Interface. Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Graphical Interface. Feb 14 14:04:59 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes... Feb 14 14:04:59 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes. Feb 14 14:04:59 raspberrypi systemd[1]: Startup finished in 2.206s (kernel) + 22.232s (userspace) = 24.439s. Feb 14 14:05:04 raspberrypi dhcpcd[496]: eth0: no IPv6 Routers available Feb 14 14:05:14 raspberrypi systemd[1]: Time has been changed Feb 14 14:07:15 raspberrypi systemd[1]: Starting LSB: Starts The Onion Router daemon processes... Feb 14 14:07:16 raspberrypi tor[586]: Starting tor daemon...Feb 14 14:07:16.092 [warn] Could not bind to 0.0.0.0:9001: Address already in use. Is Tor already running? Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.098 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 14 14:07:16 raspberrypi systemd[1]: tor.service: control process exited, code=exited status=1 Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.103 [err] Reading config failed--see warnings above. Feb 14 14:07:16 raspberrypi systemd[1]: Failed to start LSB: Starts The Onion Router daemon processes. Feb 14 14:07:16 raspberrypi systemd[1]: Unit tor.service entered failed state. Feb 14 14:07:16 raspberrypi tor[586]: failed. > On 14 Feb 2016, at 23:05, Volker Mink <volker.mink(a)gmx.de> wrote: > > Hey there. > > I recently updated my working TOR Exit from Raspian Wheezy to Jessie and also updatet my TOR-Version. > > Now I got the problem, that the TOR-service wont start when I have the ORPort in the torrc-file enabled. > Port 9001 is forwarded at my router and the Pi is also in the DMZ. Can you please send us the Tor log messages? They usually say why Tor won't start. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

3 2

TOR service wont start with ORPort enabled
by Volker Mink 14 Feb '16

14 Feb '16

Hey there. I recently updated my working TOR Exit from Raspian Wheezy to Jessie and also updatet my TOR-Version. Now I got the problem, that the TOR-service wont start when I have the ORPort in the torrc-file enabled. Port 9001 is forwarded at my router and the Pi is also in the DMZ. ## Required: what port to advertise for incoming Tor connections. ORPort 9001 pi@raspberrypi:~ $ sudo /etc/init.d/tor start [....] Starting tor (via systemctl): tor.serviceJob for tor.service failed. See 'systemctl status tor.service' and 'journalctl -xn' for details. failed! pi@raspberrypi:~ $ pi@raspberrypi:~ $ systemctl status tor.service * tor.service - LSB: Starts The Onion Router daemon processes Loaded: loaded (/etc/init.d/tor) Active: failed (Result: exit-code) since So 2016-02-14 13:03:51 CET; 43s ago Process: 18693 ExecStop=/etc/init.d/tor stop (code=exited, status=0/SUCCESS) Process: 10377 ExecReload=/etc/init.d/tor reload (code=exited, status=0/SUCCESS) Process: 18777 ExecStart=/etc/init.d/tor start (code=exited, status=1/FAILURE) pi@raspberrypi:~ $ ) pi@raspberrypi:~ $ journalctl -xn No journal files were found. pi@raspberrypi:~ $ Any ideas what to do? Best, volker

2 1

relayor 0.1.0-alpha released
by nusenu 13 Feb '16

13 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, relayor is an ansible [1] role for tor relay operators. relayor makes use of tor's "OfflineMasterKey" feature [2] to help protect your ed25519 master keys by not exposing it to the relay at all. Since that requires regular key renewals (default: every 30 days, configurable) this role aims to make this step easy by reducing it to a single command. https://github.com/nusenu/ansible-relayor Main benefits for a tor relay operator ====================================== * security: ed25519 master keys are kept offline * easy key renewal with a single command * security: every tor instance is run with a distinct user * automatically makes use of IPv6 IPs (if available) * automatic MyFamily management * automatic multi-instance setup (configurable) Supported Platforms =================== * FreeBSD * Debian 8 * CentOS 7 * Ubuntu 15.10 * Fedora 23 * OpenBSD (starting with OpenBSD's next release: 5.9) Installation ============ relayor is available via galaxy: ansible-galaxy install nusenu.relayor https://galaxy.ansible.com/nusenu/relayor/ Documentation ============== https://github.com/nusenu/ansible-relayor/blob/master/README.md https://github.com/nusenu/ansible-relayor/wiki playbook examples: https://github.com/nusenu/ansible-relayor/wiki/relayor-playbook-examples migration steps https://github.com/nusenu/ansible-relayor/wiki/Migration-Steps git tags are signed with: pub 4096R/4D705DE9 2016-02-11 Key fingerprint = A7B5 DB91 CE04 C9E0 BE66 446B 8CBE 52BD 4D70 5DE9 uid ansible-relayor signing key (https://github.com/nusenu/ansible-relayor) feedback is appreciated. regards, nusenu [1] https://docs.ansible.com/ansible/intro_getting_started.html [2] https://trac.torproject.org/projects/tor/wiki/doc/TorRelaySecurity/Offli neKeys -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWv3qoAAoJEFv7XvVCELh0H9IP/i7rRh3zrGRiru4uSOjZKUtB Fni5jqCxS29V2GKNIXt075M/osd/ZEcTeBPieHvsfQn1t1Ju4e2HwIt9yjENNycM Hg2VDkJt2wRxIg7hOHihGRqqxY7f85FLOpj4y11EskZMKFosOWJ8DrfBCGxYgLLf vVbPEyS454Kj3ezX5BXQsmMAm97tCWeMLwG1BBLnkA+ift0A+/SHU85vYYLGUdPw htZfxe83+WteziNhm8qOVw0sYlJwU8GAghFGeK/y1oPAUb0SjK9D2UHvldM6YNs8 +9359V2kHLMdqWZawellxxnbMNxjpEoHUlMDLpvmuN/S/MtBOkRGeST8bwVM1kRM NHWn3NfmoKDt1NVBqTHY8RfmG+ODr9AXzyP9q9khNlN+R72r60kPgX8+vGR06g9j 7oFi5t+0SlWK+vExEyl+bLTA74ps3GBpk+w9zM2rhX9hms3pn5AAEDzHANY6YxB7 YCpvd/cpykQFQKo6fvmuk0Igdy91rvVPh21eV2boD8qTQ2eVazNj5NLju+9gpUiW oRBN44v23KBXx+lgGb3FeNbSuzlh63MgQ6W9l7A985mfjyo0Xzw71NT5EjbC0eyM t0rdKY2byjUNOFNzb1emYVeujVIpyZqbyU/9opQGPWo7gDtDm4LwZLLBE/fD01ej F0rvBB9VpGIEp+hrWit+ =+F/t -----END PGP SIGNATURE-----

1 0

Re: [tor-relays] Re-Install Tor on raspberry, keep torrc and fingerprint
by Volker Mink 08 Feb '16

08 Feb '16

Thanks!! I will try this! ==== Message: 3 Date: Sun, 7 Feb 2016 14:58:19 +0100 From: ZEROF <security(a)netmajstor.com> To: tor-relays <tor-relays(a)lists.torproject.org> Subject: Re: [tor-relays] Re-Install Tor on raspberry, keep torrc and fingerprint Message-ID: <CANkaMAkdWFS7zLmgvjO8_b8aigDMeC6QniWq8vtBTEva9Qjb-A(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hey Volker, Indeed, like Pierre said, backup all keys not only private key, backup torrc as well. Then you can reinstall your Pi. And about ControlPort, read: https://www.reddit.com/r/TOR/comments/2haw9s/having_some_issues_with_arm_and _tor_relay/ Cheers! ************

1 0

Re: [tor-relays] Re-Install Tor on raspberry, keep torrc and fingerprint
by Volker Mink 08 Feb '16

08 Feb '16

Thanks, i will try this! === Message: 1 Date: Fri, 5 Feb 2016 13:41:07 +0100 From: "Pierre L." <petrus(a)miosweb.mooo.com> To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] Re-Install Tor on raspberry, keep torrc and fingerprint Message-ID: <56B49863.2090506(a)miosweb.mooo.com> Content-Type: text/plain; charset="windows-1252" Hey Volker, Never tried this, but there's something in the FAQ about this... https://www.torproject.org/docs/faq.html.en#UpgradeOrMove I remember some people saying you need to save every keys (and not only 1 as said in the FAQ), if I'm not wrong, in Raspbian you can find them in /var/lib/tor/keys And in the torrc, check this/// //DataDirectory /var/lib/tor/ I'm not sure, and I'm sadly noob with Tor, but this easy solution can be tried quickly I think... + when I check on my Raspbian (Jessie), debian-tor is the user/group by default on the directory /var/lib/tor I always launch arm with this command : sudo -u debian-tor arm Your /etc/tor/torrc config file has been overwritten by the upgrade ? Have you check it ? Good luck!

1 0

How to prevent netscan usage?
by Roland 'ValiDOM' Jungnickel 07 Feb '16

07 Feb '16

hi, I'm operating a tor exit with a relatively high bandwith rate for more than 3 years. My ISP receives more and more abuse tickets about my server regarding netscans. These netscans are executed with dest. port 80 so I'm not able to block them easily. Any idea how to prevent netscans using my exit node? Below you find an extract of such an abuse mail. Thanks a lot! ValiDOM Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 41518 => 46.20.92.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 41545 => 46.20.92.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 41575 => 46.20.92.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45219 => 59.192.63.xx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45218 => 59.192.63.xx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45217 => 59.192.63.xx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 42460 => 59.203.179.x 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 42517 => 59.203.179.x 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 42569 => 59.203.179.x 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 57564 => 59.211.15.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 57596 => 59.211.15.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 57631 => 59.211.15.xxx 80 Wed Nov 18 12:55:27 2015 TCP 88.198.14xxx 58022 => 59.228.86.xxx 80 Wed Nov 18 12:55:27 2015 TCP 88.198.14xxx 58046 => 59.228.86.xxx 80 Wed Nov 18 12:55:27 2015 TCP 88.198.14xxx 58081 => 59.228.86.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 37123 => 64.238.74.xx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 37178 => 64.238.74.xx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 41003 => 65.20.53.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45785 => 65.186.130.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45850 => 65.186.130.xxx 80 Wed Nov 18 12:55:26 2015 TCP 88.198.14xxx 45907 => 65.186.130.xxx 80 Wed Nov 18 12:55:12 2015 TCP 88.198.14xxx 60607 => 66.87.185.xxx 80 Wed Nov 18 12:55:12 2015 TCP 88.198.14xxx 60611 => 66.87.185.xxx 80 Wed Nov 18 12:55:12 2015 TCP 88.198.14xxx 60613 => 66.87.185.xxx 80 Wed Nov 18 12:55:14 2015 TCP 88.198.14xxx 52693 => 69.191.200.xxx 80 Wed Nov 18 12:55:14 2015 TCP 88.198.14xxx 52740 => 69.191.200.xxx 80 Wed Nov 18 12:55:14 2015 TCP 88.198.14xxx 52783 => 69.191.200.xxx 80 Wed Nov 18 12:55:27 2015 TCP 88.198.14xxx 35453 => 71.54.215.xx 80 Wed Nov 18 12:55:27 2015 TCP 88.198.14xxx 35464 => 71.54.215.xx 80 Wed Nov 18 12:55:12 2015 TCP 88.198.14xxx 39263 => 101.249.145.xxx 80

6 9