I had a very similar experience with them half a year ago.
Before i bought the service i asked them if exits are allowed and how they
act in case of abuses.
Their answer was that exits are allowed and they will find a solution
together with me in case of abuses.
Three months later the second
Am Do., 17. Sept. 2020 um 20:51 Uhr schrieb Toralf Förster <
toralf.foers...@gmx.de>:
> On 9/16/20 1:05 AM, Michael Gerstacker wrote:
> > the only relay i don't want to be a fallback anymore is a fallback now
>
> Maybe OT but I'm just curious about the reason
Am Mo., 27. Juli 2020 um 02:31 Uhr schrieb Nick Mathewson <
ni...@torproject.org>:
> On Fri, Jul 24, 2020 at 1:36 PM David Goulet
> wrote:
> >
> > On 24 Jul (13:30:31), David Goulet wrote:
> > >
> > > The new list has been generated and can be found here:
> >
> > Apology, clarification needs to
>
>
> https://medium.com/@nusenu/how-malicious-tor-relays-are-exploiting-users-in-2020-part-i-1097575c0cac
>
>
So in other words when the destination website does not really care about
their users safety and the user sends unencrypted exit traffic through Tor
then an exit relay operator could do
Am Fr., 24. Juli 2020 um 19:36 Uhr schrieb David Goulet <
dgou...@torproject.org>:
> > In tor binary:
> >
> https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fallback_dirs.inc
>
> The generated list that ended up in the binary. Thus this list needs to be
> reviewed for
Am Mi., 8. Juli 2020 um 19:37 Uhr schrieb gus :
>
> Will it have the same address and port for the next 2 years?
>
> Search [2] and [3] for your relay fingerprint or IP address and port.
>
> Keep the same IP address, keys, and ports.
>
> We need fast relays that will be on the same IP address and
Am So., 5. Juli 2020 um 18:36 Uhr schrieb nusenu :
> Hi,
>
> I'm currently writing a follow-up blog post to [1] about a large scale
> malicious tor exit relay operator
> that did run more than 23% of the Tor network's exit capacity (May 2020)
> before (some) of it got reported to the bad-relays
Am Mo., 22. Juni 2020 um 22:28 Uhr schrieb nusenu :
> I would assume that operators running relays in an end-to-end correlation
> position [1] due to incomplete MyFamily configuration are not considered
> eligible to run a directory authority.
>
> [1]
I have a relay on Focal Fossa and it required some research for me too but
this is the repository you need to add.
deb https://deb.torproject.org/torproject.org focal main
deb-src https://deb.torproject.org/torproject.org focal main
Am Mo., 1. Juni 2020 um 10:36 Uhr schrieb Pac-Man :
> When
Am Fr., 17. Apr. 2020 um 10:20 Uhr schrieb NOC :
> I said most not 100%. My exits were in a Datacenter yet they showed up at
> my home. Actually it depends who it is. The local police here was very
> friendly and send me a invitation to visit them in cases with computer
> fraud that were made
Am Do., 9. Apr. 2020 um 15:39 Uhr schrieb Clément Février <
clem...@forumanalogue.fr>:
> Hello,
>
> I often check my relay trough Metrics, but it often appears as offline
> after some time, from couple of hours to few days. I think it has this
> behavior since December 20. However, my relay seems
I just found out that i can have more than one MyFamily line specified in
the torrc.
nusenu could you please check with your tool that everything is correct now?
Greatz
Michael
___
tor-relays mailing list
tor-relays@lists.torproject.org
Am So., 23. Feb. 2020 um 11:51 Uhr schrieb Moritz Bartl <
mor...@torservers.net>:
> On 22.02.20 15:51, Michael Gerstacker wrote:
> > I am the operator of my relays so if i for whatever reason decide to not
> > publish that i run a bigger family then this shou
elay operators take some risks, but we do our best to
> reduce those risks.
>
> MyFamily is about user and operator safety. We pay more
> attention to arguments based on safety.
>
> On 22 Feb 2020, at 23:02, Michael Gerstacker <
> michael.gerstac...@googlemail.com> wro
Am Sa., 22. Feb. 2020 um 17:11 Uhr schrieb nusenu :
> Michael Gerstacker:
> >>> But as long as my family is still a small
> >> It is rather hard, time consuming and error prone
> >> to asses group sizes without proper MyFamily declarations.
> >>
Am Sa., 22. Feb. 2020 um 15:17 Uhr schrieb nusenu :
> >> - risk reduction for tor users
> >> MyFamily declarations allow the tor client software to automatically
> >> detect relay families when creating circuits to
> >> avoid using multiple relays from the same operator in a single circuit.
> >>
Hi nusenu
Am Fr., 21. Feb. 2020 um 22:24 Uhr schrieb nusenu :
> Hi Michael,
>
> > Last week i got an email with a warning that some of my relays are
> > missing the correct MyFamily setup and that i am a risk to do
> > end-to-end correlation attacks together with a list of all relays i
> >
Last week i got an email with a warning that some of my relays are
missing the correct MyFamily setup and that i am a risk to do
end-to-end correlation attacks together with a list of all relays i
operate plus one relay which uses the same name than i use but is not
operated by me.
I already knew
Hi teor,
> > On 18 Feb 2020, at 06:10, Michael Gerstacker <
> michael.gerstac...@googlemail.com> wrote:
> >
> > Once the consensus diffs are processed the load drops to normal.
> > After some time without anything noticeable for me in the debug logs the
&
> what say the logfile ?
>
Once the consensus diffs are processed the load drops to normal.
After some time without anything noticeable for me in the debug logs the
CPU suddenly jumps to 100% again and stays there till another consensus
diffs are arriving.
Its not as worse as it was the first
>
> I hope more people do come on board of this discussion now!
>
I dont think that there should be a fixed percentage about how much one
person is allowed to add.
"We need more relays ... but not from you! We don't reject your
fingerprints because we don't think that you are malicious but we
Hi,
for diversity purposes and curiosity i decided to choose Windows Server
2019 together with TheOnionPack for my first exit relay.
But before it even started to process any user traffic the CPU from time to
time gets maxed out for several minutes what makes it ugly to operate a
relay on
Am Di., 22. Okt. 2019 um 19:04 Uhr schrieb :
> On 22.10.2019 18:53, Michael Gerstacker wrote:
>
> > when i comment out the MyFamily line with an # in the torrc on one
> > relay it
> > seems to be still handled like before.
> >
> > Hitting x in nyx or waiting a
Hi,
when i comment out the MyFamily line with an # in the torrc on one relay it
seems to be still handled like before.
Hitting x in nyx or waiting a few days or rebooting does not make any
change.
Is this expected?
I expected that relay to show as part of no family now and listed as
"Alleged
Hi,
when i setted up my relays i choosed 443 as the ORPort.
My thought behind it was that 443 is most likely not blocked and less
likely observed because the ISP could expect to anyway only see encrypted
data so a Tor connection will more likely slip through it.
I let the DirPort on 9030 because
Hi
Am Do., 5. Sept. 2019 um 04:12 Uhr schrieb Mike Perry <
mikepe...@torproject.org>:
> How can we fix that for you, or at least, how can we make it easier to
> run the very latest stable series Tor on your relay?
>
When i started my first relay i had zero knowledge about Linux so i can
Yep makes sense now.
Thanks for clearing this Roger:)
Am Fr., 30. Aug. 2019 um 10:31 Uhr schrieb Roger Dingledine <
a...@torproject.org>:
> On Fri, Aug 30, 2019 at 05:52:22PM +1000, teor wrote:
> > The default value for AuthDirFastGuarantee is still 100 KB.
> >[...]
> > 6/9 authorities use
Hi Torproject,
as far as i can see my relay currently can advertise 560 KiB/s. That are
573,44 KB/s.
43C7BC2E17FB26B204EC0BD9AA784E4736979087
Following your dir-specs it should get the "Fast" flag if it can provide
more than 100KB/s.
Hi Torproject,
i think about enabling AvoidDiskWrites 1 on all my relays and not only on
my Pi because the prices for the VPS are anyway cheap as f*ck so i think
saving the provider a few disk writes is a nice deal.
In the manual it is described as:
*AvoidDiskWrites* *0*|*1* If non-zero, try to
Hi!
Good to hear that you guys try to solve the problem of slow measured relays.
For example when i measure my relay
40108FDFA40EDB013F7291F3B4DA3D412ED3A5EF
with the speedtest from tele2 i get about 90 MiB download and about 50 MiB
upload but Tor measures it with about 15 MiB.
Some of my
Hi,
i wanted to run my bridge on 443 too but i had the same problem on Raspbian
Buster with Tor 0.4.0.5
I asked Google but choosing a port above 1024 was the only thing that made
it working for me.
Am Fr., 19. Juli 2019 um 11:52 Uhr schrieb :
> > On July 19, 2019 at 6:36 AM Ben Riley wrote:
>
Hey guys,
my relay
79E683340B80676DCEB029E48FBD36BC66EBDA1E
told me:
Jul 06 15:22:34.000 [notice] DoS mitigation since startup: 0 circuits
killed with too many cells. 150515 circuits rejected, 16 marked addresses.
0 connections closed. 104 single hop clients refused.
Jul 06 16:23:25.000 [warn]
Hi,
i run 17 Entrys and one bridge at the moment.
I dont plan to change the IP adresses or the ports and most of them are
already paid for nearly two years and i dont see a reason to switch them
off after that time so if more fallback directory mirrors are needed then
feel free to add them:
33 matches
Mail list logo
