> it does not make
> sense to run a Tor relay in a vm.
The value of a limited environment is in case the
tor daemon gets exploited. A full vm needed, tor's
not an OS, so perhaps not. A static tor in an equivalent
of lighter BSD jail, probably a fair balance. A dynamic tor
in full access OS [root]
Ok, so you’re going to censor your IP address even though it’s getting
broadcasted worldwide through not only the atlas search engine, but the Tor
network itself.
If you run a relay, expect to have your IP address broadcasted. In addition, if
you run a relay, expect that that some way to conta
> Tor Project infra. is being DDoSed right now. What little that can be
> done, is being done.
Maybe you could update your DNS records to create a round robin with some of
the trusted mirrors to take the load off?
Paul
609662E824251C283164243846C035C803940378
On 2/24/18 17:25, tor wrote:
>> Relay search appears to be down right now.
>
> It seems the website (https://www.torproject.org) and package repos (ex:
> deb.torproject.org) are currently down as well.
>
> Anyone working on it?
>
Tor Project infra. is being DDoSed right now. What little that
> Relay search appears to be down right now.
It seems the website (https://www.torproject.org) and package repos (ex:
deb.torproject.org) are currently down as well.
Anyone working on it?
___
tor-relays mailing list
tor-relays@lists.torproject.org
h
El 24/02/18 a las 19:54, Spiros Andreou escribió:
> Hi Olaf,
>
> SSH brute force attacks are commonplace on any internet facing server with
> port
> 22 open. You have a number of countermeasure options:
>
> 1) install fail2ban which will block anyone who fails a login 3 times
libpam-abl could b
>> Feb 24 10:45:08.000 [warn] You are running Tor as root. You don't need to,
>> and you probably shouldn't.
You should set the User option to an unprivileged user in your torrc.
> On 25 Feb 2018, at 04:59, s7r wrote:
>
> The IP addresses of all relays in the network are public and not
> cons
Hi Olaf,
SSH brute force attacks are commonplace on any internet facing server with port
22 open. You have a number of countermeasure options:
1) install fail2ban which will block anyone who fails a login 3 times
2) move SSH to a non standard port (preferably >1000)
3) reconfigure SSH to only al
On 02/24/2018 08:36 PM, Olaf Grimm wrote:
> I am now on my server with SSH and get the message during login:
Choose another port for SSH login and close all in-ports except ssh, ORPort and
DirPort.
Configure it in /etc/ssh/sshd_config (eg.: "Port 12345") and for convenience
define this in your l
when you logof from your server must you close the port 22.
can you portforward the 22 to another ?
regards Steffen
TorGate
torgate(at)linux-hus.dk
OpenGPG 7FD5 65EF A4EF EEF3 7A13 4372 8409 49D6 01A2 0890
> Am 24.02.2018 um 20:36 schrieb Olaf Grimm :
>
> Dear guys,
>
>
> I am now on my s
Dear guys,
I am now on my server with SSH and get the message during login:
...
Last failed login: Sat Feb 24 14:22:47 EST 2018 from 5.188.10.179 on
ssh:notty
There were 1343 failed login attempts since the last successful login.
...
This simple relay (no exit) is online since less days. Loc
peter.zehet...@liwest.at wrote:
> Hi there!
>
> I try to configure a tor relay on an whonix-gateway but I allways
> receive the answer that my server has not managed to confirm that its
> ORPort and its DIRPort are rechable.
>
> How can I fix this?
>
> Thanks Peter
>
If you're using whonix-gat
Hi there!
I try to configure a tor relay on an whonix-gateway but I allways receive the
answer that my server has not managed to confirm that its ORPort and its
DIRPort are rechable.
How can I fix this?
Thanks Peter___
tor-relays mailing list
tor-rel
Gabe D. wrote:
> Feb 24 10:45:08.668 [notice] Tor 0.3.2.9 (git-64a719dd25a21acb) running on
> Linux with Libevent 2.0.19-stable, OpenSSL 1.0.1t,
> Zlib 1.2.7, Liblzma N/A, and Libzstd N/A.
> Feb 24 10:45:08.668 [notice] Tor can't help you if you us
Feb 24 10:45:08.668 [notice] Tor 0.3.2.9 (git-64a719dd25a21acb) running on
Linux with Libevent 2.0.19-stable, OpenSSL 1.0.1t,
Zlib 1.2.7, Liblzma N/A, and Libzstd N/A.
Feb 24 10:45:08.668 [notice] Tor can't help you if you use it wrong! Learn how
Hi,
Am 24. Februar 2018 18:24:07 schrieb "Gabe D." :
Hey Guys,
Ive an issue... I wanted to aid the network and setup a tor exit node,
however its failing to do so, everything looks perfect config wise and it
says "publishing server descriptor" no errors but the node never shows up
in tor at
> On 25 Feb 2018, at 04:23, Gabe D. wrote:
>
> Hey Guys,
> Ive an issue... I wanted to aid the network and setup a tor exit node,
> however its failing to do so, everything looks perfect config wise and it
> says "publishing server descriptor" no errors but the node never shows up in
> tor at
On Sat, Feb 24, 2018 at 12:23:34PM -0500, Gabe D. wrote:
> Ive an issue... I wanted to aid the network and setup a tor exit node,
> however its failing to do so, everything looks perfect config wise and it
> says "publishing server descriptor" no errors but the node never shows up in
> tor atlas
Hey Guys,
Ive an issue... I wanted to aid the network and setup a tor exit node, however
its failing to do so, everything looks perfect config wise and it says
"publishing server descriptor" no errors but the node never shows up in tor
atlas, is there something i may be doing wrong?
This is my
19 matches
Mail list logo