[tor-relays] Bridge acting strange

2020-12-29 Thread enrollado
I have noticed some bizarre behavior on one of my relays.

I logged into the server hosting particlefive (bridge) on November 15 and 
noticed that the tor process had crashed (not a clean exit). I had accounting 
set up, so it had hibernated from 11/07 00:00 UTC to 11/07 00:44 UTC. After 
that, it appeared to be running normally, but it crashed sometime after 11/07 
06:25 UTC. I don't have crash dumps enabled, so I don't have any information on 
the crash. I restarted it and it appeared to have been working normally. I 
checked on it again on the 16th and all was well. On December 2nd, it suddenly 
stopped receiving client connections. According to the metrics page, it hasn't 
passed any traffic since then, though the logs show 20 - 60 GB per heartbeat 
interval. The log rotation has gone strange as well. As of today:

notices.log - 12/29 06:25 to 12/29 12:20
notices.log.1 - 12/28 06:25 to 12/29 06:20
notices.log.2 - 11/06 06:25 to 11/07 06:25
notices.log.3 - 12/26 06:25 to 12/27 06:25
notices.log.4 - 12/25 06:25 to 12/26 06:25
notices.log.5 - 12/23 06:25 to 12/24 06:25

So, the log from the day before the crash is still hanging around with no 
unusual activity shown, and I'm missing the log file for 12/24. At this point, 
it seems to be running normally, but it is not receiving any new connections.

Yesterday, I changed the configuration from accounting to bandwidth limiting, 
so notices.log.1 has the hup I sent to reload the configuration. However, 
notices.log.3 also shows a hup signal at 06:25 UTC that I did not send.

I should probably report this on the tor-dev list, but moderation on that list 
appears to be pretty slow, and this list is more active. I was wondering if 
anyone else has seen this kind of odd activity on a bridge before. My paranoia 
alarm is in yellow status, so I'm about to dump this relay, get a new IP, and 
start over.

Any advice is appreciated.

No me preguntas nada, no te digo una mentira.
Enrollado

Sent with ProtonMail Secure Email.

publickey - enrollado@protonmail.ch - 0x5923AD04.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] SSH

2020-12-29 Thread George

On 9/21/20 7:52 AM, Logforme wrote:

On 2020-09-21 11:19:20, "Андрей Гвоздев"  wrote:


Hello
I'm running a TOR relay, every time I SSH to my server I see a message
that there were thousands of failed login attempts
Do you see this message too?


Exposing a SSH server to the internet will get you lots of login attempts.


Yes, this is normal for anyone running internet-facing systems, and 
there are as many mitigations as there are sysadmins.



Here are some things you SHOULD do to help the situation:
Change the SSH default port.


Yes, this will lessen the number of entries in the relevant log file 
until the brute force attackers get more intelligent. Just understand 
this is not a security measure. It's more like a dose of obscurity to 
make log files less noisy.



Disable the root login.


+1


Use key-based authentication.


+1

Those are important and vital security measures, as is employing some 
sort of multi-factor authentication methods like Yubikey. (no, 
officially key-based SSH auth is not formally MFA...)


But the two ways to actually address the problem is either:

* network or host-based firewalling to limit connections based on the 
same source, rate, etc., which depends on the operating system you're 
running.


* there are also tools like fail2ban and so on that are popular.

* if you're running FreeBSD or NetBSD, try Christo's blacklistd. It 
might be ported to other OSs. If it's not, it should be...


HTH

g
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Relay operators meetup @ rC3: today 22:00 UTC+1

2020-12-29 Thread kantorkel

To avoid confusion: We will meet today at 21:00 UTC, that is 22:00 CET

https://www.starts-at.com/event/2603308559



On 12/29/20 12:30 PM, kantorkel wrote:

Hi all,

the meetup will take place today, 2020-12-29, at 10pm UTC+1.

In rC3 world, we will meet in the bottom right corner of the Jena hackerspace 
"Krautspace" 
(https://rc3.world/rc3/room/5edc1329-f55c-46e1-a739-b0d642c2c80f/). Please use 
https://jitsi.rc3.world/torrelayops-724b5 to join from the outside world.

Thanks to qbi for organizing the room.

Best
kantorkel

On 12/27/20 10:54 PM, Stefan Leibfarth wrote:

Hello Tor friends and relay operators,

I haven't heard of a relay operators meetup at the ongoing rC3.
Are there any plans?
If not, who of you is interested?

It would be my pleasure arrange a session.
Please get back to me.

Cheers
Leibi

___
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


Re: [tor-relays] M1 anyone?

2020-12-29 Thread Amogh Pradeep
Hey Nifty,


Orbots been shipping tor binaries that run on ARM for a while now, so it
should be possible to run on an M1 no problem!

The app has also supported relaying for a while now, so should be possible.

Hope the pointer helps!


Best,

amoghbl1

On 12/29/20 9:58 AM, niftybunny wrote:
> With one of my servers down and giving me brain cancer … anyone tried to run 
> relays on the new M1 chip? Is it even officially supported right now? Anyone 
> any idea how much it could push?
>
>
> cheers,
>
> nifty
>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


pEpkey.asc
Description: application/pgp-keys
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Relay operators meetup @ rC3: today 22:00 UTC+1

2020-12-29 Thread Volker Mink
Thanks for this info. 
Will join!

> Am 29.12.2020 um 13:45 schrieb kantorkel :
> 
> Hi all,
> 
> the meetup will take place today, 2020-12-29, at 10pm UTC+1.
> 
> In rC3 world, we will meet in the bottom right corner of the Jena hackerspace 
> "Krautspace" 
> (https://rc3.world/rc3/room/5edc1329-f55c-46e1-a739-b0d642c2c80f/). Please 
> use https://jitsi.rc3.world/torrelayops-724b5 to join from the outside world.
> 
> Thanks to qbi for organizing the room.
> 
> Best
> kantorkel
> 
>> On 12/27/20 10:54 PM, Stefan Leibfarth wrote:
>> Hello Tor friends and relay operators,
>> I haven't heard of a relay operators meetup at the ongoing rC3.
>> Are there any plans?
>> If not, who of you is interested?
>> It would be my pleasure arrange a session.
>> Please get back to me.
>> Cheers
>> Leibi
>> ___
>> 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


Re: [tor-relays] Relay operators meetup @ rC3: today 22:00 UTC+1

2020-12-29 Thread kantorkel

Hi all,

the meetup will take place today, 2020-12-29, at 10pm UTC+1.

In rC3 world, we will meet in the bottom right corner of the Jena hackerspace 
"Krautspace" 
(https://rc3.world/rc3/room/5edc1329-f55c-46e1-a739-b0d642c2c80f/). Please use 
https://jitsi.rc3.world/torrelayops-724b5 to join from the outside world.

Thanks to qbi for organizing the room.

Best
kantorkel

On 12/27/20 10:54 PM, Stefan Leibfarth wrote:

Hello Tor friends and relay operators,

I haven't heard of a relay operators meetup at the ongoing rC3.
Are there any plans?
If not, who of you is interested?

It would be my pleasure arrange a session.
Please get back to me.

Cheers
Leibi

___
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


Re: [tor-relays] Relay operators meetup @ rC3

2020-12-29 Thread Jens Kubieziel
Am Sun, Dec 27, 2020 at 10:54:44PM +0100 schrieb Stefan Leibfarth:
> I haven't heard of a relay operators meetup at the ongoing rC3.
> Are there any plans?

I'm in the process of organizing something. There is a Jitsi room in the
Chaoszone (Krautspace): https://visit.at.rc3.world/as/krautspacejena
We will do it probably around 2200 UTC this evening.
The announcement will follow. 

-- 
Jens Kubiezielhttps://kubieziel.de/blog/
  https://datenkanal.org/
  https://insecurity.radio.fm/
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Tor Traffic De-prioritization Script

2020-12-29 Thread Roger Dingledine
On Wed, Dec 23, 2020 at 05:47:11AM -0800, tontu wrote:
> I recently acquired a server with "unlimited" (not unmetered) bandwidth
> on a non-Hetzner/OVH/Scaleway network, but the pipe is just 100mbit (and
> will be saturated at some points by personal traffic bursts). That being
> said, I expect the 100mbit pipe to be idle 90% of the time, so it
> doesn't seem ideal to just set a low BandwidthRate.
> 
> The documentation [1] for relay bandwidth shaping options points to a
> script to de-prioritize Tor traffic to ensure that personal traffic
> takes precedence.
> 
> However, the script no longer exists within Tor source code. [2] Is this
> script now deprecated? If not, where can I find it? If so, what
> alternative methods might exist to de-prioritize Tor traffic during
> bursts from personal traffic pipes on Linux or BSD systems?

It looks like yes, we removed it:
https://gitlab.torproject.org/tpo/core/tor/-/issues/29434
https://lists.torproject.org/pipermail/tor-relays/2019-February/016995.html

So it definitely counts as deprecated, in the sense that nobody maintained
it for a long time and then somebody deleted it. :)

But that said, I bet it would still work, or at the very least, it would
be a good set of hints for how to write a new one. If you do write an
updated one, please share it here.

You can find a copy in earlier git branches, e.g.:
https://gitweb.torproject.org/tor.git/plain/contrib/operator-tools/linux-tor-prio.sh?h=maint-0.3.5

Hope this helps!
--Roger

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays