This none of sense make.
On 7 January 2014 07:27, francisco fabiano wrote:
> THIS IS A FAKE TOR, GOT SURELY NOW
>
>
> On 7 January 2014 02:19, Matthew Harrold wrote:
>
>>
>> On 7 Jan 2014 01:56, "I" wrote:
>> >
>> > Is there a way to open ports for Tor as an VPS account holder?
>> >
>> > Robert
I've run several middle relays for over a year but they keep getting
knocked down due to circuit creation storms (on RPIs) or powercuts or
updates or some other issue. Yes uptime is important, but 100% is not
practical for most relay operators. Also, if you want a shirt so badly,
donate to Tor! In
Hi Robert, the design of Tor is such that it is not possible to determine
what traffic inside the network is from the malware so you won't be able to
block it as a relay, this is the way Tor has to work to ensure privacy. If
the malware is exiting to the clearnet then determining which port it is
u
Dnsdynamic.org is quite nice. Simple and easy, decent update API. Never had
a problem in the 2 years I used them.
My 2 satoshi...
On Dec 18, 2013 1:20 PM, "Oliver Schönefeld"
wrote:
> hello to everybody,
>
> as there were some alternatives for dynmic DNS handling mentioned, i'd
> like to add the
Isnt it just:
kb = kilobits
kB = kilobytes
using standard convention...?
On 17 December 2013 12:38, Kiss Gabor (Bitman) wrote:
> Dear folks,
>
> I'm tor relay operator since several years but newbie on this list.
>
> I just moved node 'traktor' from physical host to virtual machine.
> So I re
I don't think you need to specify an external IP in the torrc file. You can
just specify 0.0.0.0:9050 for socks and 0.0.0.0:9030 for directory. Tor
will identify if you have a dynamic IP and resync with the network
automatically each time it changes. Also make sure it is a relay you are
running and
This is true. Some websites download lists of all relays and just mass
block the ips. Its usually webmasters who have no idea how tor works and
don't realise that a middle relay poses them no threat whatsoever. This is
why education is best. If someone is blocking your IP, just email them
explainin
If you want to continue using skype, you could invest in a VPN just to hide
it from your ISP and make microshaft think you are coming from a different,
non-tor related IP.
Tom
On 6 November 2013 15:12, Eugen Leitl wrote:
> On Tue, Nov 05, 2013 at 09:59:11AM -1000, Ryan Winner wrote:
>
> > Use
I agree with mick that dropping packets is more secure, though probably bad
practice. If everyone did this then, yes, the network would suffer on
average but when securing a vital server, e.g a tor node, i think it is
acceptable.
It really doesnt make it any harder to troubleshoot since any service
What is the fingerprint of your exit node, maybe someone here can take a
look?
Also, use iptables! If it is a dedicated VPS then drop anything you dont
recognize, leaving only Tor ports (9001,9030 default) and maybe a service
port like 22 for SSH for something. Port 9050 should not be visible from
This is something I raised a few months ago. I found that an reinstall of
an old relay defaulted to exit, I only noticed after a few days... since
the relay was on a residential address I immediately reconfigured it.
I would assume that the majority of users who run relays on vps in the
cloud will
I run a few Rasp PI relays. If you use Tor 2.3.5 you need to limit
bandwidth to 100KB or less and make sure the CPU is not overclocked to
avoid heating issues unless you stick it in the fridge or something.
2.4.17 is much better at dealing with circuit storms, i can push 3Mbps
upstream with no iss
Hi Jan,
Here is an example config for shorewall, pulled it straight off a relay I
run.
# PORTPORT(S)
DESTLIMIT GROUP
SECTION NEW
# Drop Ping from the "bad" net zone.. and prevent your log from being
flooded..
#P
Sorry, also your /etc/shorewall/policy file should read:
net all DROPnotice
# The FOLLOWING POLICY MUST BE LAST
all all REJECT notice
to allow for whitelisting in rules file.
Regards,
T
On 3 October 2013 21:03, Thomas Hand
There was a version of Tor released in the development repos that included
Accept *.* in torrc. I remember seeing it but have no idea which version it
was. I too think this is a mistake. If casual relay operators are being
shut down due to a misconfigured torrc, Tor will suffer more bad press by
me
Hi Gordon,
I'm having a little trouble installing your deb files using sudo dpkg -i.
Am I missing something.
Thx. Tom
On Aug 18, 2013 12:36 AM, "Gordon Morehouse" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Good news, everyone!
>
> Lance Hathaway:
> > Speaking only for myself
I tend to kill almost all logging and use AvoidDiskWrites 1 (or whatever it
is) in torrc. Also your log files will fill up a lot faster if you are a
directory server.
On 12 August 2013 02:18, TonyXue wrote:
> I checked the old notices.log file.
>
> The warning of unable to write just came out f
You would need to remove the tor keyfile before creating the image so that
a new hash is made of each new node when they first run tor. Other wise
might get loads of nodes with same hash, not sure what that would mean for
network. I am also running a pi relay and would like a copy of the tweaks
you
Hi Nick,
I was in a similar boat to you for a while. Also UK based with adsl and a
dynamic IP. I found that running a non-exit relay node is fine so long you
limit bandwidth usage in torrc. Wouldn't recommended exit relay unless you
want to deal with your ISP.
If you only run a relay then the censo
Hi torsion,
I'm also running a tor relay on a raspberry pi and keep getting these storm
creation events which crash the box. You said you made some adjustments to
the configs to get a more stable system? Can you please email me copies of
the configs or maybe list the changes you made?
I'm trying t
I'm also having some problems with my rpi node going down every few days
due to lack of resouces and needing a reset. Can you mail me with some of
the alterations you made which might make it more stable? Thanks. T
On Jun 5, 2013 10:42 AM, wrote:
> I've been seeing these storms as well on my rela
21 matches
Mail list logo
