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
Hi,
I am trying to setup Tor relaying, but it doesn't work so far.
Windows 8, private vpn.
I opened ports 80,443,9001 and 9030 (both TCP and UDP) on my Comcast router
to be forwarded to the box I'm trying to configure.
I added inbound and outbound rules in the firewall setup for ports
80,443,9001
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
> 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
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
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
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.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
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
https://metrics.torproject.org/rs.html#details/53CDD268FAD52B0236A4E7F4784259A41C6E3414
‐‐‐ Original Message ‐‐‐
On 24 February 2018 5:59 PM, s7r wrote:
> 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
You're currently not measured, per atlas it's been only 12 hours since this
node has been online. It takes about three days to get a nominal measurement.
I had a node on a 200mbps connection sit at 0bps for two days straight, then
it finally had some movement in the evening of day three. I would
You should at least change the ssh port immediately now that you have published the address.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Sat, Mar 15, 2014 at 02:56:36PM -0800, I wrote:
> You should at least change the ssh port immediately now that you have
>published the address.
No, this is bad advice.
First because Tor relays (and their addresses) are public anyway.
And second because having an ssh port exposed to the Intern
On Sat, Mar 15, 2014 at 08:46:44PM +, eugene zhukovsky wrote:
> I am trying to setup Tor relaying, but it doesn't work so far.
> Windows 8, private vpn.
> I opened ports 80,443,9001 and 9030 (both TCP and UDP) on my Comcast router
> to be forwarded to the box I'm trying to configure.
> I added
Roger,
I beg your pardon. I would not want "fud" to deter new relays. I think the
risks are overplayed as it is.
It was only that it was published on this list. I published the relay nickname
somewhere and regret it.
I suggested the port change because that is what the VPS operators have tol
Thank you very much Roger for the advice.
I can't seem to make it work, so I'll just try setting it up on a different
box
---
Best wishes,
Eugene Zhukovsky
On Sun, Mar 23, 2014 at 11:12 AM, I wrote:
> Roger,
>
> I beg your pardon. I would not want "fud" to deter new relays. I think
>
On Sun, 23 Mar 2014 03:12:47 -0800
I allegedly wrote:
>
> I suggested the port change because that is what the VPS operators
> have told me was the first thing to do to avoid being constantly
> 'hacked' which has happened over and over to me.
Actually I agree that moving ssh from the standard p
Hi, is anything misconfigured?
please tell me how to "change the ssh port"
cheers, Curare
-Original-Nachricht-
Betreff: Re: [tor-relays] Tor relay setup
Datum: Sat, 15 Mar 2014 23:56:57 +0100
Von: I
An: tor-relays@lists.torproject.org
You should at least change th
Hi,
should be fine from now on?
changed ssh to very high port.
sadly it seems my consensous weight is lost! :(
cheers, Curare
-Original-Nachricht-
Betreff: Re: [tor-relays] Tor relay setup
Datum: Tue, 25 Mar 2014 08:21:56 +0100
Von: "curare...@t-online.de"
An: &
19 matches
Mail list logo
