Hi all,
I have been operating the relays
- Bazinga B198C0B4B8C551F174FBB841A172616E3DB3124D
- JPsi2 F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521
for about 10 years.
The hosting provider stops providing their current service and their
successor services are not Tor-friendly anymore.
Hence, these
Exit relays have nothing to do with .onion sites.
By design you cannot block them in your relay.
On 5/27/21 6:43 PM, Tor Operator wrote:
> Hello, exit node operator here. I share the values of the TOR
> foundation, that’s why I’m operating an exit node but I can’t unsee all
> the bad it is used f
Happens on all internet-facing ssh daemons.
Independently of tor.
On 3/31/21 6:35 PM, Cristiano Kubiaki Gomes wrote:
> Hi there,
> O noticed many ssh requests to my Debian VM running a Relay and I am
> wondering if this is normal or if this is happening only with me.
>
> Anyone else see this ssh
I believe to have observed a worrying pattern lately.
A small number of people select a person for a perceived or actual
wrongdoing and do their best at destroying their target's lives though
any and all means available. Including by exerting pressure on their
target's workplace to throw the target
On 10/12/20 12:55 PM, William Kane wrote:
>> The provider said it was due to Spectre mitigations and the only way for me
> to fix this would be to switch to a newer (more expensive) plan...
>
> What?
>
> Your provider lied to you / scammed you, Spectre/Meltdown etc.
> mitigations have nothing to
0
SOCKSPolicy reject *
RunAsDaemon 1
ControlPort 9051
HashedControlPassword
16:28CD63819CB35660601EB9CED4BC2A4252D3DB80488DFD4F22CA4AE930
ORPort 9001
ORPort [2a00:1158:3::1ba]:9001
Nickname JPsi2
RelayBandwidthRate 12500 KB
RelayBandwidthBurst 12500 KB
ContactInfo 0xF1ADC390 Random Tor No
On 10/07/2016 12:55 PM, Zac wrote:
> that my uptime on Atlas is reset to zero when I need to restart
> the service, i.e. for updates or configuration changes.
> Is this expected behaviour
Yes
signature.asc
Description: OpenPGP digital signature
___
t
On 09/28/2016 02:01 PM, Chad MILLER wrote:
> So? A relay can always have behaved badly. What's the harm in you
> fraudulently claiming to be in family com.example.chadmiller ? A user's
> path won't have passed through both you and me, but you could have
> prevented traffic from passing through you
On 05/22/2016 04:00 PM, Markus Koch wrote:
> Yes, but how many ports do I have to open to be "useful"? In an
> extreme case: Would it help just to forward port 80 and 433?
I think the most spartanic Exit Policy is at the bottom of [1]:
ExitPolicy accept *:53# DNS
ExitPolicy accept *:80
I don't have any exit relays, but my understanding is that you should
use torrc, and only torrc, to define which outgoing ports you want to be
reachable.
Do not block or otherwise interfere with anything which you allow in
torrc, because that may get you the BadExit flag when discovered.
A Reduce
On 05/20/2016 01:18 PM, Pascal Terjan wrote:
> I haven't been able to access BA website from home for the last few weeks.
>
> I have failed to get any other answer on the phone that to try using
> Internet Explorer or to wait for things to maybe get fixed. Twitter
> support was not more helpful.
>
On 25.04.2016 11:45, Petrusko wrote:
> 4. I'm confused, the "bridge" is acting like a relay ? (like a router on
> a network, 50% upload / 50% download...?). Or like a hidden door to
> contact the Tor network, and the client will only use relays after
> without the bridge ?
> (I don't want this serv
On 08.03.2016 19:30, Volker Mink wrote:
> You can take it down for some days without losing any flags or consensus
> weight.
> Had it with my exit i have at home.
> I had to reinstall it and i have the same stats as before.
The HSDir flag will be cleared after each restart of the Tor daemon, a
On 26.02.2016 00:19, Stephen R Guglielmo wrote:
> I have a VPS with 512 MB RAM. [...] The relay is an entry guard and moves
> about 20 MB/s.
Is that really 20 MegaByte per second?
If so, I fear 512 MB RAM won't cut it.
According to my experience, for a 100 Mbit/s relay you need at least 1
GB RA
On 26.02.2016 13:50, Roman Mamedov wrote:
> On Fri, 26 Feb 2016 12:27:07 +0100
> Random Tor Node Operator wrote:
>
>> So in terms of censorship resistance, bridges with occasionally changing
>> IP are better for the Tor network than those with static IP.
>
>
On 26.02.2016 11:54, Tim Wilson-Brown - teor wrote:
>
>> On 26 Feb 2016, at 11:52, Random Tor Node Operator
>> mailto:t...@unterderbruecke.de>> wrote:
>>
>> On 26.02.2016 05:15, torser...@datakanja.de
>> <mailto:torser...@datakanja.de> wrote:
>>
On 26.02.2016 05:15, torser...@datakanja.de wrote:
> * Next, i noticed a frequent (daily) behavior of the Tor server
> dropping traffic to around zero. Inspecting this, let me to
> understand, my provider was disconnecting me and reassigning a new
> IP on a daily basis, which took som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.02.2016 22:12, Tom van der Woerdt wrote:
> Op 23/02/16 om 22:10 schreef Toralf Förster:
>> Louie Cardone-Noott:
>>> Those like me running debian and putting off doing a reboot
>>> might find needrestart (package of same name) and checkrestart
>>>
Hi,
you didn't get the V2Dir flag with AccountingMax set on... I had to have
the same experience with that.
Random Tor Node Operator
hi
Am 13.12.2015 um 23:32 schrieb Lucas Werkmeister:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all!
For some reaso
hmm weight-drops again? i am loosing my whole traffic / consensus
weight... since 7 pm CET.
Random Tor Node Operator
Am 09.12.2015 um 01:27 schrieb Tim Wilson-Brown - teor:
On 9 Dec 2015, at 06:07, tor-server-crea...@use.startmail.com
<mailto:tor-server-c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 28.11.2015 17:43, David Schulz wrote:
> can i get problems as an german citizen with an non exit tor relay
> in germany with an italien ip? not realy or? i think of TMG § 8.
As a non-exit relay operator, you are most certainly not going to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.05.2015 13:23, Sharif Olorin wrote:
>> Any idea ? or its normal ?
>
> I'm not sure, but I also saw this for the first time today after
> enabling ipv6 on a relay last week. A quick look at the relevant
> code doesn't shed any immediate light on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.12.2014 12:20, Roger Dingledine wrote:
> Has anybody else here seen messages like this?
Some days ago I had a message like that on my relay JPsi2
(F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521).
Tor's memory consumption is rather high there lately.
O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No
> such file or directory
According to a stackoverflow page [2], you can look for hints
indicating the existence of AES-NI support in "sysctl hw" and
/var/run/dmesg.boot
> PID USERNAM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/01/2014 08:46 PM, s7r wrote:
> I have multiple relays running on the following systems: - vmware
> vsphere virtualization technology - 100 mbps port - 1GB dedicated
> RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64
> or Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/2014 07:24 PM, ja...@icetor.is wrote:
> Hello all, This is something that's bothered me for quite some
> time. I often use arm
> (https://www.torproject.org/projects/arm.html.en) for monitoring
> my relays and to keep a quick eye on things lik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/28/2013 01:26 AM, I wrote:
> I think two months is a bit short to be rewarded with a t-shirt
> from donated resources.
>
> It makes more sense to extend the time but include the total time
> running ignoring minor disruptions.
I agree with that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 02:18 PM, Stephan wrote:
> On 11.09.2013 13:33, Random Tor Node Operator wrote:
>> Could you post the corresponding line(s) in your monitrc?
>
> Of course. I use the default of "set daemon 120", so tor is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 12:34 PM, Stephan wrote:
> I'm just taking a wild guess here, because I had similar symptoms:
> that log message doesn't seem to be a crash but a regular shutdown.
> In my case I use 'monit' to monitor my server and the running
> services
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 12:37 PM, Roger Dingledine wrote:
>> In my case I use 'monit' to monitor my server and the running
>> services - including tor. Once in a while the automated TCP check
>> on either the OR-Port or the DIR-Port failed which resulted in
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody,
since this botnet started flooding Tor, my Tor relay Bazinga
($196832C61F30E9D6D179393C9AED4E47FD29796B) has been experiencing some
issues.
Previously, it was relaying 100 Mbit/s for a few months without problem.
When the botnet came
31 matches
Mail list logo
