Re: [tor-relays] relay not receiving very much traffic

2014-05-18 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 5/19/2014 12:48 AM, zwie...@quantentunnel.de wrote:
> I see, network admin. Good to have you back again. If you can push 
> 850Mbit from an university we should bring it to run. I am on
> midrange machines LE 100Mbit/s. We could go through some details
> (torrc) here or you check '
> https://www.torservers.net/partners.html ' for higher skilled
> advice.
> 
> Felix
> 
> *Gesendet:* Sonntag, 18. Mai 2014 um 23:28 Uhr *Von:* "Markus
> Klock"  *An:*
> "tor-relays@lists.torproject.org"
>  *Betreff:* Re: [tor-relays] relay
> not receiving very much traffic Well, I *am* the network admin :) 
> This server is directly connected to our backbone and is not being 
> throttled in any way. AS1653 is our upstream and they like the 
> Tor-project, no throttles there either :) How often does tor/atlas
> mesure bandwith?
> 
> /Markus 
> 
>
> 
Från: zwie...@quantentunnel.de
> Skickat: ?2014-?05-?18 23:11 Till: tor-relays@lists.torproject.org 
> Ämne: Re: [tor-relays] relay not receiving very much traffic
> 
> Your provider is 'Student network in Vasteras/Eskilstuna'
> (mdfnet.se), AS1653 SUNET Swedish University Network? Sounds like a
> shared connect. You can talk to the admins? Please check the
> university Tor recommendations.
> 
> I could connect through $94F9D8D35C4A4851B1DAF85F70F90DB95065E81E
> as guard. Like I mentioned: Check the speed side. It seems
> Tor/Atlas measures you to 1.96MB/s.
> 
> Felix
> 
> *Gesendet:* Sonntag, 18. Mai 2014 um 21:12 Uhr *Von:*
> zwie...@quantentunnel.de *An:* tor-relays@lists.torproject.org 
> *Betreff:* Re: [tor-relays] relay not receiving very much traffic 
> Hmm. 
> https://atlas.torproject.org/#details/94F9D8D35C4A4851B1DAF85F70F90DB95065E81E
>
> 
https://consensus-health.torproject.org/
> both look good as well.
> 
> You are sure your speed is like promised? You tried a speed test
> like iperf with a second server?
> 
> Felix
> 
> 
> *Gesendet:* Sonntag, 18. Mai 2014 um 20:31 Uhr *Von:* "Markus
> Klock"  *An:*
> "tor-relays@lists.torproject.org"
>  *Betreff:* Re: [tor-relays] relay
> not receiving very much traffic This is my relay: 
> http://torstatus.blutmagie.de/router_detail.php?FP=94f9d8d35c4a4851b1daf85f70f90db95065e81e
>
>  regards, /Markus /
> 
> 
>
> 
From: zwie...@quantentunnel.de
> To: tor-relays@lists.torproject.org Date: Sun, 18 May 2014 19:28:21
> +0200 Subject: Re: [tor-relays] relay not receiving very much
> traffic
> 
> Hi Markus
> 
> can you please tell your Fingerprint? You checked your consensus?
> 
> Felix
> 
> *Gesendet:* Sonntag, 18. Mai 2014 um 18:59 Uhr *Von:* "Markus
> Klock"  *An:*
> "tor-relays@lists.torproject.org"
>  *Betreff:* [tor-relays] relay not
> receiving very much traffic Hello! I deployed a new tor-relay about
> 2 months ago. It runs on a server with 2 Quad-cores, 8GB RAM and
> 1Gbit connection. However, I have still not received very much
> traffic to it, it almost never goes above 10Mbit. This is the
> server traffic the last 2 months: 
> http://best-practice.se/dump/tor-ralay.PNG
> 
> Is this normal or may I have configured something wrong? Last time
> I had a relay running I received 100Mbit+ traffic...
> 
> /Markus/ ___ tor-relays
> mailing list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays 
> 
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays 
>  
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays 
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays 
>  
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 


Atlas does not always show the exact speed, at my relays sometimes it
goes up sometimes down.
In vidalia I can see my relays with 7 - 8 MB/s and atlas will show
them for 5.2 MB/s. I don't know how speed is measured in atlas or how
often this happens. I think the data is imported from the bandw

Re: [tor-relays] New SSL keys for new OpenSSL version?

2014-06-16 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/16/2014 11:49 PM, no.thing_to-h...@cryptopathie.eu wrote:
> Hello Tor!
> 
> I run an internal Tor relay on Debian Wheezy. Today the OpenSSL 
> version was updated to 1.0.1e-2+deb7u11 . Do I need to delete the
> old SSL keys like after the Heartbleed bug?
> 
> Thanks and best regards
> 
> Anton
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

No, you do not need to delete the keys and you SHOULD NOT delete those
keys if not in an extreme situation.

The latest OpenSSL vulnerability was not that bad, it had a different
attack vector and an attacker could not have possibly gain your onion
keys, unlike in heartbleed, where an attacker could read data out of
your memory and theoretically compromise your onion keys.

It's a good thing you changed keys after heartbleed, but the latest
vulnerability did not have such impact so you should not do the same,
otherwise you will lose your current identity (relay), flags and all
history associated with it in the consensus.

Tor-relay mail list (subscribe if you are not subscribed) will always
tell you what you need to do, in such events. If you need to throw
away onion keys and generate new keys for an existing relay, you will
be clearly notified about it, if not, it means they were not affected.

In the latest OpenSSL bug you only needed to update OpenSSL, that's all.



- -- 
s7r
PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJTn17aAAoJEIN/pSyBJlsRKe8H/3RaRM2qS8VwpRgkwUmwI8l/
UT5hfDmCqAeyNRdBkLo46Xe32MD/qyBQg7F8U5iLO3cPHDIm1zejHzeR04rAV6T5
f8mQdx3BAotTwgVQnPAAMYbuF9MKGf2SeeKkio9M7/Udbg89t+had+FFx57j07H2
lpDKRQo8ot2lnlDe1VRlcF0hojcyddq2b7ny3hRf/I4dgT4eU2uvbFo9mXMkJYab
eNgpTge8ZguM+gGIJEYo/jA/rf2Z5e3xrdevKqjxWY0waRphXQ3Lhb06u0lG6I/w
kUM/yRC8AdVo3GbGqHAA6NiI3JHrEabxHxumsZmtircq9nYazRQszIbVhJc0x90=
=Z53i
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] normal for a new relay node to be under-utilized?

2014-06-18 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/18/2014 7:04 PM, Kali Tor wrote:
> Is it normal for a new relay node to carry almost no traffic even
> after 24 hrs?
> 
> From Atlast
> 
> Uptime: 1 day 8 hours 30 minutes and 28 seconds Advertised
> Bandwidth: 59.71 KB/s
> 
> From arm Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 160.0
> b/s)
> 
> Upload (0.0 b/sec - avg: 738.8 b/sec, total: 10.8 MB) Download
> (0.0 b/sec - avg: 3.6 Kb/sec, total: 52.2 MB)
> 
> torrcRelayBandwidthRate 2048 KB RelayBandwidthBurst 4096 KB 
> AccountingMax 100 GB AccountingStart month 1 03:00 DirPort 9030 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

Hi,

It's normal. The usage will increase, in time. Just keep your relay
running all the time and it will grow once clients learn about it.

Read: https://blog.torproject.org/blog/lifecycle-of-a-new-relay

Very important for new relays.

Keep it running and thanks for running a relay.
- -- 
s7r
PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEbBAEBAgAGBQJTobznAAoJEIN/pSyBJlsR1TcH9iUy7lJ4dtD2kHJsYhXmBHAG
+JR5AVAl+v8AswrL1nB+g+2FM8kYDRS7T9NC56l2X7BSNdiQ02w2yF51gDL7S6z4
y4UWhgR5gW5zPGG/69Z/r5l0oDJyNXS+YTy34zy9hMv6/wu+oiaU86anuesYPtBm
PrTjIsY6TlHYIKYKiYEievW4HlOvK5E0ug+CJkYWMyM8gp26qiUsbz+uOO8NP4yI
mBxgmlSvvd+VYQ1QtMVtdcqQ/LRT1jMFVkrKaMZn8G0GgFxo55pDMidCcu53iJYc
I0DHGb7EAGgS4XSb/4ItaVNhrJRV7G/uEbc6M6xKRg3NhXVdlP15Gd2YBPLNuQ==
=fMoP
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Traffic limitation

2014-06-18 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/18/2014 10:46 PM, Relay Admin wrote:
> Both has downsides but I think daily is better, if it starts to get
> a lot traffic than it will serve the network for a few hours every
> day, but in monthly if it use the all available bw in 4 days, it
> won't do anything for 26 days. I'm sure you can get a better answer
> for it from someone who limits the traffic on his/her relay.
> 
> Berkay
> 
> On June 18, 2014 9:11:57 PM EEST, johhher 
>  wrote:
> 
> Hi,
> 
> I'm running a Tor relay on a cheap Linux vserver with high
> bandwidth. I have a traffic limitation of 500Gb per month and was
> just wondering what would be the best configuration for the
> network. Currently I've limited the traffic to a daily maximum to
> prevent it from hibernating a long time at the end of the month. Is
> this the right way to do it? Or would be better to limit it on a 
> monthly basis.
> 
> Thanks for an answer! Johhher 
> 
>
>  tor-relays mailing list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
That is quite a low limit for a monthly cap. If it is a high speed
server it will consume the traffic within 5 days, after some time and
it's known in the consensus and gains some flags.

I think you are better of putting accounting per day, a daily limit of
16GB should do it. Or, see if you negotiate with your provider
unlimited traffic :) long shot worth to try

- -- 
s7r
PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJTofVAAAoJEIN/pSyBJlsRmnsIALOSA29lsMED59ELox99J7td
UKelAVzbusfvxxXIeEUW2sCYT1RTIuPhZHzT2VjrflNpppk9f9DDRQgAdB29LQeL
+A4r1fjUvFYOJwUzgMirwJG+MpwjWxkLcujTTzRL4dh7eGVMffEOiNwm5KizKGIf
Vuz1TII8sFB/wuRBXfGFy9iP7nOgAmrDR3k6Cid8rsPsKttwFHA1NNHSsqNkL/I4
/Rr7cIIytbDbsIqDvvCQNG0eCGoc2lRvLg6K1DW2fTJNsgOCxHiF6YzsbjrXRw/N
EpfkD2EajNIS2kyrM2tKnvDaU1XkGJ9ON1vf3HeXgcE/Dj9ue6dbWulV2Hz2foc=
=uUXO
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Is my tor exit relay set up correctly?

2014-06-23 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/23/2014 3:00 AM, Sander Bongers wrote:
> Hi,
> 
> A few weeks ago I setup a tor exit relay, using this documentation:
> https://www.torproject.org/docs/tor-relay-debian.html.en
> 
> I have somewhat experience, so I kinda knew what I was doing, and I
> got the message "Self-testing indicates your ORPort is reachable
> from the outside. Excellent." in the log file.
> 
> But my server doesn't seem to appear in any tor relay lists such as
> https://globe.torproject.org , even 
> after a few weeks. What could I have done wrong?
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
How could we know if you have done anything wrong given the
information you provided?

Please copy / paste your torrc file to a paste bin and send us the link
please copy / paste your tor log file to a pastebin and send us the link
please type ifconfig, pastebin the output and send us the link
please let us know as much as you can about your current configuration
so we may identify the problem
please let us know what tor version are you using and how did you
install it (from deian repositories, tor repo, compiled source-code, etc)

So we may help you in a professional manner.

- -- 
s7r
PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJTp9GcAAoJEIN/pSyBJlsRwHwH/3huMCzk3JdDTtalvN/1BNsS
WEDJEE/uDLeBO4gu5hSpATvp2tP+vxTObMUWtxEFEjfkxtfvJzPitWxlOpQx6ogd
AWIjPiSwp8aNMhiTO/ExiPO5Q8i03NhEsbE3gmXOHjbklPOQOTFIqL3j1gNuWG9K
OiSetdUGVE4hMz9vo08OYgPg6IHtj7DTVcji8TC9bKZgsHkhIuGCc4gUu51tkHWJ
QcTadntYmkxc1ekNGj+5HlSD1c2MjqSCh6lbCr2zPqF3bVnhsJmuypippzhc5k93
bA5NGK/c2eGbGBqXgCqx5W5drL2nHzpuS0APXsjkBqKLoUKR0KUFBYoV3ofI+pE=
=OQH7
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] KVM based virtual machine showing 4 MB/s in atlas, others showing 8-9MB/s ?

2014-06-23 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

The same virtualization technique at different providers gives me
different advertised bandwidth for relays in atlas:
one provider 8-9MB/s
other 3-4 MB/s

The relays are all exit, having the same RAM and CPU configuration, as
well as 100mbit port and unmetered traffic, they use the same Tor
version, none of them are capped in any way via torrc or other means,
same operating system and same virtualization technique. Why could be
this difference in advertised bandwidth?

Suggestions?

- -- 
s7r
PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJTqIMAAAoJEIN/pSyBJlsRTg0IAKGweB8grMmx18rB33/xBrBC
6UAbpnUxj3tDlD+7J9SwK1jkPSvxpKEkKuwblFifJ2J1o4xoUKCvQQWLVfwP4qRI
0R6cn/Zx9pShzZ6MRRIOmuxaZjiavddqeM0/qcnwhsvGVH/6sTw8VrLV2TMH
vExzu7ofEjV1205CZ1CBAj0sOW2s+3nld7iulvttWbBoeHs2+CbRpEfQu1QPoZYu
NtJ6f0vBBkenCWD/yv9Xaiwo/Ywej6jH97LIdksr9msRcDmJnbmY3VSmrlnm8n7z
YFJSCFlOi3LJIB0y8QmZuowHAQcGe0Q1LmGCWU4uGgB4OHU7QRgC/jM7qffp+eQ=
=+FWS
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Please need urgent help with the DNS resolver of a fast exit relay

2014-04-24 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

The servers from my ISP are not stable or good enough to handle the
traffic for this Tor exit router.

I get this in the log very often:
Apr 24 15:14:07.000 [notice] Circuit handshake stats since last time:
91633/91636 TAP, 15962/15962 NTor.
Apr 24 17:40:45.000 [warn] eventdns: All nameservers have failed
Apr 24 17:40:45.000 [notice] eventdns: Nameserver :53 is back up

Both nameservers fail and come back after 1 second, or less.

I don't know what impact will this have on the exit node. Is it any
problem at all?

I have decided also to setup my own DNS resolver and not use the ones
from ISP, so I have installed named.

What I need help is, for your someone to tell me exactly how do i have
to edit named.conf in order to:

1. Enable DNSSEC, for the clients who want to use it. Not make it a
requirement, just enable it and prefer it over normal DNS if and when
possible.


2. Be able to resolve all TLDs as described here:
https://trac.torproject.org/projects/tor/wiki/doc/DnsResolver#DNSResolverServer

Now I can clearly understand the message from that post but there is
no instruction anywhere about how to do it, those links for Alt Roots
are broken. Is this a requirement? Who needs to resolve silly TLDs not
supported by IANA / ICANN anyway?

3. Cache the records for as long as possible - my relay is already
using a lot of traffic so I have to spare as much as I can.


Please provide me with a good named.conf and description of settings
so I can properly configure a good DNS resolver for my relay.

Thank you in advance!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBCAAGBQJTWTnUAAoJEIN/pSyBJlsRtN8IAJK8ndrb6IdW+PRpynTu5gzH
/6ID3k3uO+EX1jKDSrSMzUlfaOZT0UIVXX/KKxqJSa4YQH4MMGcWfCYXkv+bdFC0
s3ABvAWOeklX5KxUwGWaEJJND+Zu4nstIcVTFpjKpbiFJ7mdzjlDVSCsZFXYBVoV
tOY7amgAoQCxNsG0aBKUKeArRSJ03jcicD/92PkL8ro2IB6FItusp5Qywcp12Nhq
mXEJdD8l/5jSS1epaaZJ6LzDFyyZsVKsxK8EkBxkYtblkk8WxUnkz4gXrP88cnMC
rHb8gqLBvHqjLUn1fKtmJbxJ/J1qEa+2PyoJpzkh4hQxXSZ52TskWKSi0eR7j5E=
=675a
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Please need urgent help with the DNS resolver of a fast exit relay

2014-04-25 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 4/25/2014 3:26 PM, Linus Nordberg wrote:
> "s...@sky-ip.org"  wrote Thu, 24 Apr 2014 19:20:37
> +0300:
> 
> | I get this in the log very often: | Apr 24 15:14:07.000 [notice]
> Circuit handshake stats since last time: | 91633/91636 TAP,
> 15962/15962 NTor. | Apr 24 17:40:45.000 [warn] eventdns: All
> nameservers have failed | Apr 24 17:40:45.000 [notice] eventdns:
> Nameserver :53 is back up | | Both nameservers fail and come
> back after 1 second, or less.
> 
> Are you running this relay on a BSD system, perchance?
> 
> I see this on lots of relays on FreeBSD and think that it's related
> to libevent on certain platforms. I also think that it's benign. 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 


Yeah I am running it on FreeBSD 10.0 release.

Anything I can do about it? If it's just working on normal basis
regardless this warning i can leave it like this?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBCAAGBQJTWopaAAoJEIN/pSyBJlsRdf8H/2mk3ERggvVKGmtUz4GhbXmn
9QoQWIxYA+Mp8YLXcVE1FxYOYrCYavgV/VvnJtz06TTDkNJaFYM5diLYOd1Wgcyq
BRMVt/WrojbioxCikuzovxgL3UcrmUiP0xy2gPF+p+p/Hf+nsqV/TkpywBSVyAki
QVrUWRt2fYgnXepj6W3LgogebKeQxmsU37zpm91cx6zdgzzAUmw5V5DB+H0TGRwj
a5E9walNQnDryX8Wj4WbfzSZwW9JyERnospAb+BCzsoeI6nxIlJCRmshZxWtbKHT
GKmGHQzvJG6GAKGwtzuE52EL8oedw7o576QeSJqGdlxUHPgpA6Z66PnuoFAopNQ=
=QYg0
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] SSH scans from Tor exit

2014-04-28 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 4/29/2014 1:31 AM, I wrote:
> One VPS company has just asserted that SSH scans are being run from
> my Tor exit rather than another process on the VPS. Is this
> happening to anyone else? Does anyone know what can be done to stop
> it?
> 
> Robert
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 


Could you explain with more details? Your question is not totally clear.

If your VPS is being SSH brute forced there are many ways to protect:
- - make hostbased authentication or use keys instead of password-based
authentication
- - install fail2ban to ban IPs after "x" wrong passwords
- - make sure you put a very strong password, seriously
- - disable root login via ssh
- - if you have a VPS made with KVM you can disable SSH access at all
and use the javaconsole from the VPS panel?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBCAAGBQJTXtqcAAoJEIN/pSyBJlsRyu4IAMsD1fsZeqZsMuQhCgQ2bDfW
M6rSKQjjCDXbI37W6w153rEZkSrA6cxh40t7PkcyhuWDXSSZTi/CfY2r5AzRNBxk
CKNrKioPVU28PETqJLo/8aOcmRFVZAgUYXpUwDnMCqOOW7Lun71UOzgAbyNdcOaa
ogECDzC92lkrGvN7ofy64NeBnyZ82DysNBUss1BxQ1bX5prnlSznY/0OgxYsBwsS
UCFCZ3tmcf905b7esibYinwtLlXG9Oc8PdTaBH+JV64s+m+J5DTLK6zRqDiaIpDJ
TqOQF3ALAYijDvJ+eO5JHY0whqMAWDFC6pRBDyAsok9D5AA1bkJtEXlFPe/8NLM=
=UukK
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] About running an Exit node

2014-05-07 Thread s...@sky-ip.org 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 5/7/2014 12:56 PM, Pika ohc wrote:
> Hi there,
> 
> I was considering to run an Exit node with my own pc, however, i
> have some questions about exit node.
> 

It's very nice you want to contribute to the Tor network by running a
relay. If you can spare the budget, it's always better to run a Tor
exit relay at a datacenter, on a dedicated or virtual server, and that
machine to have only on scope: Tor relay. If you go on this way make
sure you specify to the provider that it will be a Tor relay and it
will consume bandwidth more than usual.

> 1. How can I know if there is a client specifying me as an exit
> node and the traffic is sent from the client to me directly(where
> my exit node is the first node and also the last node for the
> client.)?
> 

That is not allowed by default in Tor. You don't need to do anything
to protect against  this since it won't happen. An user can trick your
exit node into thinking that "he" is a Tor relay too, but this will
not affect you in any way and it will just have terrible anonymity
impact over the so-called "attacker". This would not be something sane
to do, I mean nobody would benefit anything out of doing this, it will
just decrease their level of anonymity. This affects everyone so it's
no cause for worrying.

> 2. If i found some clients trying to do something bad by using the 
> method mentiond in 1., how can I stop him? Is iptables or anything
> else can help me to block such clients?
> 

This is irrelevant. You should not do anything and you should not even
monitor what the users are doing via your exit relay. Restrict what
you do not want to allow by using reject argument in torrc. For
example, block port 25 to prevent spam (SMTP) - this is where most
abuse comes from. And if you are in a country concerned about p2p
filesharing, reject high ports too commonly known to be used by
bittorrent. You can find on torproject.org reduced exit policy
example. Other than port 25 it's not anything else important what
somebody could do to cause harm to you relay, in the real sense of the
world. If you consider scanning or bruteforcing SSH or other services
relevant, you should not :)

If you are an exit relay, include a valid contact email address in
torrc. Run a page on port 80 of the relay's IP (DirPortFrontPage if
you use DirPort on port 80) and explain that this is a Tor exit relay,
explain in few words what Tor is and provide a valid contact email
address so concerned people can at least send you an email. You can
find this page sample just by searching on google "this is a tor exit
router".

> Hope there's someone can answer me. Thank you!
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBCAAGBQJTan5uAAoJEIN/pSyBJlsRM2sH/A+iUfN+HXm6nKjHec/nTNUx
6XMinfyWnAWuaP+9I25Y5+shu8fxQjbncYyrJVfwTOj4aRTFwa/ADeE4ERT6v+MP
kNm1h3uITst5l2zk2m4cRRkmQtOutp0S1nTJ2zS3SoTGfbzv7bkbJl3QgQyzmJ70
VcEO4AIbme4++4ske8WNh1d+2qVW3qiFWqaMoHMtiEw57O447+9FgPRHvklZ2Tn/
KzAsC01WNFQ5+rl8i8qblmuRovlSorZB22qLhR6/Qzs7aLGD5Ojp1363clXY8DfZ
qIkDY89k5LUnT1vMZIBmCbb9YuvkbkD0nSM0VbL18sgkACnLJGv9W72QFqT1Cac=
=Rg7k
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays