On Wed, Jun 18, 2014 at 9:34 PM, Zack Weinberg wrote:
> If the process listening on port 80 is the Tor process, then any
> vulnerability in the HTTP service it presents to port 80 can be
> exploited for a direct attack on the relay itself. If port 80 service
> is provided by a separate program (e
I've managed to get my relay running long enough to run the bandwidth check and
have it succeed. I'll check Atlus and it'll say my relay's up and running.
However when I check again about an hour later, it's saying that "Running:
false".
I've set up the relay recently, so I'm not expecting a lo
On Wed, Jun 18, 2014 at 5:54 PM, Rui Branco
wrote:
>
>
> In the atlas project why the tor-relays ip are discovered? isn't it
> dangerous?
>
> There is nothing strange or dangerous about that. After all your ip has
to be published somewhere otherwise no one would be able to use your relay.
You cou
Hello all,
With the upsurge of new users running relays this list has picked up a
fair amount activity. I run one of torservers.net partner organizations
called Icetor (icetor.is). In addition it handles abuse notifications
for other individuals who choose to run exit relays. This is done i
> Hmm.. what am I doing wrong here:
>
>> sudo apt-get install python-stem
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> python-stem is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
>
>> tor@KaliTorLi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/17/2014 02:09 PM, Zack Weinberg wrote:
> Tor relays get pounded on by the script kiddies -- a degree of
> hardening is appropriate. I don't know if there are any stock
> Puppet "tighten security" modules but these are the things that I
> rem
Hmm.. what am I doing wrong here:
> sudo apt-get install python-stem
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-stem is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> tor@KaliTorLinLon:~$ tor-promp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/18/2014 10:46 PM, Relay Admin wrote:
> Both has downsides but I think daily is better, if it starts to get
> a lot traffic than it will serve the network for a few hours every
> day, but in monthly if it use the all available bw in 4 days, it
> wo
Both has downsides but I think daily is better, if it starts to get a lot
traffic than it will serve the network for a few hours every day, but in
monthly if it use the all available bw in 4 days, it won't do anything for 26
days. I'm sure you can get a better answer for it from someone who limi
On Wed, Jun 18, 2014 at 1:49 PM, Alexander Fortin
wrote:
> On 18. Juni 2014 at 16:26:38, Zack Weinberg (za...@cmu.edu) wrote:
>> Best practice as I understand it is that you should have an exit
>> notice on all exit relays. What I'm not sure of is whether "DirPort
>> 80 + DirPortFrontPage" is the
On 17. Juni 2014 at 23:56:43, Zack Weinberg (za...@cmu.edu) wrote:
> Tor relays get pounded on by the script kiddies -- a degree of
> hardening is appropriate
I was thinking a little more about this point, and I’m wondering how running a
Tor relay is increasing the likeliness of being hit by sc
Hi,
I'm running a Tor relay on a cheap Linux vserver with high bandwidth.
I have a traffic limitation of 500Gb per month and was just wondering
what would be the best configuration for the network.
Currently I've limited the traffic to a daily maximum to prevent it from
hibernating a long time at
On 18. Juni 2014 at 19:49:26, Alexander Fortin (alexander.for...@gmail.com)
wrote:
> > Yes, makes sense, and should not be too complex to implement,
> I’ll try to add this and get back here for some review. Thanks for
> the feedback
https://github.com/shaftoe/puppet-tor/tree/fixes#exit-relays
18.06.2014 17:54, Rui Branco:
> hello,
> I'm a new user of the Tor-relay and I have many doubts. Sorry about that.
Are a new user of the Tor-network or do you run a relay, yourself?
You can read the FAQ about your concerns and voice your remaining questions.
> In the atlas project why the tor-re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/18/2014 8:54 AM, Rui Branco wrote:
> hello, I'm a new user of the Tor-relay and I have many doubts.
> Sorry about that.
>
> In the atlas project why the tor-relays ip are discovered? isn't
> it dangerous?
>
When I first starting using Tor and l
On 18. Juni 2014 at 16:26:38, Zack Weinberg (za...@cmu.edu) wrote:
> Best practice as I understand it is that you should have an exit
> notice on all exit relays. What I'm not sure of is whether "DirPort
> 80 + DirPortFrontPage" is the recommended way to accomplish that. The
> CMU Tor exit uses a s
Yup. Please see
https://blog.torproject.org/blog/lifecycle-of-a-new-relay
On Wed, Jun 18, 2014 at 9:04 AM, Kali Tor wrote:
> Is it normal for a new relay node to carry almost no traffic even after 24
> hrs?
>
> From Atlast
>
> Uptime: 1 day 8 hours 30 minutes and 28 seconds
> Advertised Ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/18/2014 7:04 PM, Kali Tor wrote:
> Is it normal for a new relay node to carry almost no traffic even
> after 24 hrs?
>
> From Atlast
>
> Uptime: 1 day 8 hours 30 minutes and 28 seconds Advertised
> Bandwidth: 59.71 KB/s
>
> From arm Bandwidth (
hello,
I'm a new user of the Tor-relay and I have many doubts. Sorry about that.
In the atlas project why the tor-relays ip are discovered? isn't it
dangerous?
--
Best Regards,
Rui Branco
___
tor-relays mailing list
tor-relays@lists.torproject.org
http
Is it normal for a new relay node to carry almost no traffic even after 24 hrs?
>From Atlast
Uptime: 1 day 8 hours 30 minutes and 28 seconds
Advertised Bandwidth: 59.71 KB/s
>From arm
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 160.0 b/s)
Upload (0.0 b/sec - avg: 738.8 b/sec, total
There's nothing quite as rich as Atlas, but one option is the /info
command on...
https://stem.torproject.org/tutorials/down_the_rabbit_hole.html
That said, the main purpose of this command is an advanced controller
prompt for tor. It either requires a running tor instance or will kick
one off on
Hi,
> On Wednesday, June 18, 2014 11:26 AM, "ja...@icetor.is"
> wrote:
> > I fooled around with some php json parsing in order to get my metrics
> charts working on icetor.is . I can send you the code if you'd like.
> -Jason
That would be much appreciated!
Thanks,
KaliTor
>
> On 06/18/2014
Hi,
> I'm working on that. The onion.py script in OnionPy [1] has some rudimentary
> atlas-like functionality that I hope I can soon make complete as soon as I
> find
> some free time.
>
> If you know python, it shouldn't be too hard to do that, PR's welcome!
I know enough Python to create t
On Wed, Jun 18, 2014 at 3:01 AM, Alexander Fortin
wrote:
> On 17. Juni 2014 at 23:56:43, Zack Weinberg (za...@cmu.edu) wrote:
>> It would be nice if exit-relay mode enabled an HTTP "exit notice" as
>> described at
>> https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment.
>
>
I fooled around with some php json parsing in order to get my metrics
charts working on icetor.is . I can send you the code if you'd like.
-Jason
On 06/18/2014 10:15 AM, Lukas Erlacher wrote:
> Hi,
>
> I'm working on that. The onion.py script in OnionPy [1] has some
> rudimentary atlas-like funct
Hi,
I'm working on that. The onion.py script in OnionPy [1] has some rudimentary
atlas-like functionality that I hope I can soon make complete as soon as I find
some free time.
If you know python, it shouldn't be too hard to do that, PR's welcome!
Best,
Luke
[1] https://github.com/duk3luk3/o
Hi all,
Is there a CLI client/tool that does what https://atlas.torproject.org/ does?
Basically provide an output based on a node's fingerprint?
e.g.
https://atlas.torproject.org/#details/7EDE11A41D1C7DF4F9103ABAA4F0A31E42CB0C02
Thanks,
KaliTor
___
t
On 17. Juni 2014 at 23:56:43, Zack Weinberg (za...@cmu.edu) wrote:
> Why do you disable directory mirroring? It's my understanding that
> this should basically always be on.
Not sure why, I think at the beginning I wanted to use the ‘minimal’ config,
and I didn’t even now about directory services
28 matches
Mail list logo