On Fri, Oct 4, 2019, at 11:51 AM, Paul Templeton wrote:
> Just an FYI on a problem I found with two DNS of 1and1 ionos.
> The affected DNS are 212.227.123.16 and 212.227.123.17 which both are
> not responding to *.torproject.org domain or sub domains.
> I found this out as my system reverted
On Wed, Feb 7, 2018, at 4:45 PM, Karsten Loesing wrote:
> Possible disadvantages are:
> - If somebody runs a relay and a bridge, both with the same contact
> information, a censoring adversary might guess that the bridge might run
> on a nearby IP address as the relay. However, they could as
On Thu, Jan 25, 2018, at 10:09 PM, teor wrote:
>
>
> Only 4 of the 9 directory authorities can make a direct connection to
> your relay: (large page)
> https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.html#FE4033D750831C32A957174ADD11E40F558A14A9
>
> The required
On Sun, Oct 15, 2017, at 12:49 PM, teor wrote:
>
> > On 15 Oct 2017, at 07:26, Geoff Down <geoffd...@fastmail.net> wrote:
> >
> >> On Sun, Oct 15, 2017, at 01:51 AM, teor wrote:
> >>
> >>> On 14 Oct 2017, at 20:33, Geoff Down <geoffd...@f
On Sun, Oct 15, 2017, at 01:51 AM, teor wrote:
>
> > On 14 Oct 2017, at 20:33, Geoff Down <geoffd...@fastmail.net> wrote:
> >
> > Hello all,
> > what sort of crazy bug would make Tor give different hashes for the same
> > password?
>
Hello all,
what sort of crazy bug would make Tor give different hashes for the same
password?
$ tor --hash-password hello
16:735E6FA5355D4146606AFE25B61B411DF419878C99705164D038FC99BC
$ tor --hash-password hello
16:8201E7D35BB8CACB60BF8947B49A3480BA1A17E77EDA8BE45790746884
$ tor --version
Tor
Dear operator of relays Necto4 etc.
Please remove OpenDNS filtering of any sort from your exit relays.
Note that abuse-team@necto.onion (as per your port 80 page) is not a
routeable email address.
GD
--
http://www.fastmail.com - IMAP accessible web-mail
On Mon, May 15, 2017, at 10:20 AM, Roger Dingledine wrote:
> On Tue, Mar 28, 2017 at 02:22:17PM +0100, Geoff Down wrote:
> > 72 hours now on 2.9.9 with no clock jumps. Still occasional timeouts as
> > per above.
>
> Hi Geoff,
>
> Any news on your strange clock jump
On Mon, May 15, 2017, at 10:20 AM, Roger Dingledine wrote:
> On Tue, Mar 28, 2017 at 02:22:17PM +0100, Geoff Down wrote:
> > 72 hours now on 2.9.9 with no clock jumps. Still occasional timeouts as
> > per above.
>
> Hi Geoff,
>
> Any news on your strange clock jump
On Fri, Mar 24, 2017, at 01:35 PM, Geoff Down wrote:
> I'm still getting occasional read timeouts (via Polipo) from a
> site that
> is entirely reliable over clearnet, and occasional 'Failed to receive
> SOCKS5 connect request ack' from another site when using curl in
> so
On Fri, Mar 24, 2017, at 07:35 AM, teor wrote:
> >
> > On 21 Mar 2017, at 01:42, Geoff Down <geoffd...@fastmail.net> wrote:
> > ...
> > The usual SIGINT shutdown hangs as well - have to send a second SIGINT.
> What is ShutdownWaitLength set to in your torrc or d
On Tue, Mar 21, 2017, at 09:27 AM, teor wrote:
>
> Can you try setting an explicit IP address for your bridge, using:
> Address NNN.NNN.NNN.NNN
> in the torrc?
>
> We might not have fixed all instances of this issue in 20423.
>
Done, (SIGINT still hadn't shut down after 10 minutes btw) then
On Mon, Mar 20, 2017, at 01:44 PM, teor wrote:
> >> Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection
> >> to [scrubbed]:80. Giving up.
>
> We fixed a bug like this in 0.2.9.6-rc.
>
> It was caused by DNS resolves that received no reply and didn't timeout.
> (DNS
On Mon, Mar 20, 2017, at 01:44 PM, teor wrote:
>
> > On 21 Mar 2017, at 00:09, Geoff Down <geoffd...@fastmail.net> wrote:
> >
> > More information:
> > Mar 20 10:48:23.000 [warn] Your system clock just jumped 38788 seconds
> > forward; assuming establish
.
On Sun, Mar 19, 2017, at 02:20 PM, Geoff Down wrote:
> Further information.
> Curl error
> Failed to receive SOCKS5 connect request ack.
> and from earlier, Tor log
> Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection
> to [scrubbed]:80. Giving u
Further information.
Curl error
Failed to receive SOCKS5 connect request ack.
and from earlier, Tor log
Mar 19 11:52:37.000 [notice] Tried for 32496 seconds to get a connection
to [scrubbed]:80. Giving up.
--
http://www.fastmail.com - A no graphics, no pop-ups email service
On Thu, Jan 19, 2017, at 02:33 AM, teor wrote:
>
> > On 19 Jan 2017, at 13:30, Geoff Down <geoffd...@fastmail.net> wrote:
> > Then a HUP produced the same sequence (but a different PID), with no
> > sign of the lines you mention above regarding 'restart'.
> > The
On Thu, Jan 19, 2017, at 01:14 AM, teor wrote:
>
> > On 19 Jan 2017, at 12:00, Geoff Down <geoffd...@fastmail.net> wrote:
> > Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
> > Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method
> &g
Hi,
I sent a SIGHUP to the tor process after altering the torrc and got this
effect:
Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method
error. (obfs3 Could not set up listener (0.0.0.0:x) for 'obfs3'
(Address already
Would the operator of the above mentioned exit please remove OpenDNS
'Malicious URL' filtering.
Thanks,
GD
(PS having a .onion contact address doesn't work, I think)
--
http://www.fastmail.com - Same, same, but different...
___
tor-relays mailing
See
https://trac.torproject.org/projects/tor/ticket/21045
but perhaps there is some flag required.
--
http://www.fastmail.com - Access all of your messages and folders
wherever you are
___
tor-relays mailing list
You are unlikely to make any friends at the host or tsrget site by
publishing the attack logs.
Just sayin'.
GD
On Fri, Oct 28, 2016, at 04:57 AM, Markus Koch wrote:
> Getting abuse mass mails on nearly all exist in the last hours:
>
--
http://www.fastmail.com - Email service worth paying for.
On Mon, Oct 10, 2016, at 04:28 PM, Andreas Krey wrote:
> On Mon, 10 Oct 2016 15:15:46 +0000, Geoff Down wrote:
> ...
> > Needless to say, the disk is not full and 'tor' can write to that
> > directory just fine now.
>
> Question is whether it was full (or o
Hi all,
these are the last entries in my log, but my bridge is still listed on
Atlas and client functionality is fine. Latest stable version on
OSX10.4.
Needless to say, the disk is not full and 'tor' can write to that
directory just fine now.
Oct 05 22:52:09.000 [warn] Couldn't open
On Fri, Jun 17, 2016, at 09:30 PM, Michael Armbruster wrote:
> Hi Paul,
>
> assuming the default HTTP port, it was an attack to the port 80.
> Furthermore, the cryptic looking signs (%XX, whereas X is 0-9 or A-F),
> are url escaped characters. Unescaping them leads to something like this:
>
>
You can be either a relay (with your IP address public) or a bridge
(with your IP address known only to the Bridge Admins and the users, as
long as it has changed since you ran a relay).
And the way to run as a Bridge is to add
BridgeRelay 1
to your torrc: the ports that need to be open are the
On Thu, Dec 10, 2015, at 04:52 AM, Yawning Angel wrote:
> On Thu, 10 Dec 2015 01:26:41 +
> Geoff Down <geoffd...@fastmail.net> wrote:
>
> [snip[
> > It's quite annoying that Tor doesn't remember its auto-picked port,
> > and I have to change the p
Hello all,
a couple of quick questions.
Tor exited with this error:
Dec 09 06:35:34.000 [err] descriptor at 0x62ee080 begins with unexpected
string "". Is another process running in our data directory? Exiting.
I've a vague feeling it's happened once before - anything to worry
about?
Also, on
On Sun, Oct 25, 2015, at 07:52 PM, Moritz Bartl wrote:
> On 10/25/2015 08:26 PM, Geoff Down wrote:
> >> If so, I'll write a small something that will allow adding new subdomains
> >> to it. So that you can always add and update subdomains on it.
> > As long as yo
On Sun, Oct 25, 2015, at 05:49 AM, Eran Sandler wrote:
> If so, I'll write a small something that will allow adding new subdomains
> to it. So that you can always add and update subdomains on it.
As long as you don't let other people do that themselves. That would be
open to abuse.
GD
--
On Tue, Sep 22, 2015, at 03:51 AM, Tim Wilson-Brown - teor wrote:
>
> > On 22 Sep 2015, at 12:00, Geoff Down <geoffd...@fastmail.net> wrote:
> >
> > Hi Tim
> >
> > On Tue, Sep 22, 2015, at 01:40 AM, Tim Wilson-Brown - teor wrote:
> >>
&g
A query using Globe stalls at the 'processing - please wait' stage, so I
assume the problem is actually with Onionoo.
GD
--
http://www.fastmail.com - Same, same, but different...
___
tor-relays mailing list
tor-relays@lists.torproject.org
Hi Tim
On Tue, Sep 22, 2015, at 01:40 AM, Tim Wilson-Brown - teor wrote:
>
> > On 21 Sep 2015, at 19:59, Geoff Down <geoffd...@fastmail.net> wrote:
> >
> > Hi all,
> > is anyone willing to talk me through getting Obfsproxy working on
> > OSX10.4?
Hello all,
I'm trying to set up a Bridge/Client Tor instance with the following
torrc:
ControlPort 9051
ExitPolicy reject *:*
HashedControlPassword
Nickname
ORListenAddress 0.0.0.0:9001
ORPort 80
BridgeRelay 1
ContactInfo
Should this work as a bridge? Client functionality is fine (port 80
the 'package' as installed, I am at a loss.
Regards,
Geoff Down
--
http://www.fastmail.com - Access your email from home and the web
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
t effect in the docs.
I did get a 'Self-testing indicates your ORPort is reachable from the
outside' message eventually - there was just a 12 minute wait between
'Bootstrapped 100%' and 'Guessed our IP address as', the reachability
test followed immediately after.
>
> On Monday, Sept
On Sat, Sep 12, 2015, at 11:37 PM, Tor Relay @ WeFu.Org wrote:
> It appears that First Tech Federal Credit Union is blocking all Tor
> nodes (including non-exit nodes) from connecting to their website,
> http://www.firsttechfed.com
>
> This seems ... misguided on their part. Blocking exit
On Tue, Jul 14, 2015, at 03:05 PM, Karsten Loesing wrote:
I implemented most of the changes that Julius and I suggested plus the
feedback we received on this list. Please find the updated ExoneraTor
service here:
https://exonerator.torproject.org/
Please give it a try, including the
On Tue, Jul 7, 2015, at 07:47 PM, Zack Weinberg wrote:
The thing is, putting myself in the shoes of someone trying to
investigate an incident, I think the distinction among this relay has
_never_ allowed any sort of exiting, this relay _does_ allow exiting
right now, and this relay _did_
On Tue, Jul 7, 2015, at 10:12 PM, Zack Weinberg wrote:
On Tue, Jul 7, 2015 at 4:50 PM, Geoff Down geoffd...@fastmail.net
wrote:
If someone only has an IP address for an incident but no exact time,
they barely have the basis for a complaint, let alone something more
formal like
On Sun, Jul 5, 2015, at 02:26 PM, Karsten Loesing wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/07/15 14:20, teor wrote:
On 5 Jul 2015, at 19:37 , Karsten Loesing
kars...@torproject.org wrote:
Actually, how about we use the same definition as for the Exit flag?
On Sat, Mar 14, 2015, at 08:56 AM, Sasikantha babu wrote:
Mar 14 02:36:06 NoNameForHost Tor[4403]: Our IP Address has changed from
49.205.4.174 to 188.165.200.138; rebuilding descriptor (source:
46.105.44.4).
Since the IP 46.105.44.4 is the same in both cases, and that IP reported
my
On Tue, Mar 10, 2015, at 06:30 AM, Sasikantha babu wrote:
Hi all,
Today on my relay I observed the below messages 2 hours back. Tor
reported address change from IP_IN_INDIA
to IP_IN_FRANCE from SRC_1. The next second SRC_2 reported address
change from IP_IN_FRANCE to
On Sat, Dec 6, 2014, at 12:10 AM, TT wrote:
Busting down doors is pretty much spot on about the reason i am
unwilling to run the relay on my own IP address: i've read enough news
about overzealous law enforcement in my country (non-Tor related, but
still), and i'm certainly not going to
On Sun, Nov 2, 2014, at 11:53 PM, flapflap wrote:
I:
Unused slower middle nodes would be better turned into bridges wouldn't
they?
I doubt that's still possible since their IP adresses are already
published and probably blacklisted.
___
On Tue, Apr 15, 2014, at 01:03 AM, Chris Whittleston wrote:
Right - so this seems to confirm that they are indeed blocking Tor - and
not just exits - I'm running a middle relay.
I've contacted them via a web form asking why they block all Tor relay
IPs.
Tips on what I should tell then
On Tue, Feb 4, 2014, at 05:18 PM, K. Besig wrote:
Why shouldn't I be concerned when, by simply accessing this page, all my
actual ip/dns information is readily available to all?
Because that's how Tor works. Every relay has to be able to connect to
every other relay (apart from Bridges) so the
On Wed, Oct 23, 2013, at 04:09 PM, Karsten Loesing wrote:
The measurements will work best if you have the scamper tool from
the Cooperative Association for Internet Data Analysis (CAIDA)
installed (see the README for installation instructions).
Your README should probably explicitly say that
On Tue, Oct 15, 2013, at 10:00 PM, Roger Dingledine wrote:
On Tue, Oct 15, 2013 at 04:17:31PM -0400, starli...@binnacle.cx wrote:
Hello,
Hello starlight,
You're not using mailing lists properly. The right way to do it is to
send your mail and wait. Not to resend variations of your mail
On Sat, Aug 31, 2013, at 05:32 PM, Pascal wrote:
http://torstatus.blutmagie.de indicates that only 21.4% of Tor nodes are
exit nodes. Are we wasting this precious resource by running non-exit
traffic through these nodes?
-Pascal
No. The non-exit traffic masks which relay the exit traffic
On Sun, Aug 18, 2013, at 12:35 AM, Gordon Morehouse wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Good news, everyone!
Lance Hathaway:
Speaking only for myself (in turn), this is something I would
desperately like to see. I've been planning on deploying several
Raspberry Pis
On Sat, Apr 14, 2012, at 07:15 AM, Steve Snyder wrote:
I often get abuse complaints from icecat,biz saying that a RIP attempt
was seen from the IP address of my exit node. Apparently this involves
too many connections in a given period of time.
I've tried to contact them but get no answer
On Tue, Jan 24, 2012, at 11:01 AM, Justin Aplin wrote:
My bad, I wasn't thinking straight when I wrote that. I forgot the
openssldir, at least on OSX, doesn't actually contain the libs. Try sudo
find / -iname libssl*.dylib to find an appropriate lib in your setup.
Since I replaced my system
On Mon, Jan 23, 2012, at 02:33 PM, Nick Mathewson wrote:
On Mon, Jan 23, 2012 at 2:27 PM, Geoff Down geoffd...@fastmail.net
wrote:
Can anyone help with this please?
% sudo ./configure --with-libevent-dir=/opt/local/lib/ make make
install
- checking for libevent directory
On Mon, Jan 23, 2012, at 06:24 PM, Justin Aplin wrote:
On 1/23/2012 2:56 PM, Geoff Down wrote:
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
_EVP_sha256
_RSA_generate_key_ex
_SHA256
_SHA256_Final
_SHA256_Init
_SHA256_Update
_CRYPTO_ctr128_encrypt
On Mon, Jan 23, 2012, at 10:06 PM, Justin Aplin wrote:
I'm kind of flying in the dark here (being unfamiliar with macports),
but I think a proper --with-openssl-dir= statement will help. Run
openssl version -a, check the version number to make sure it's the new
version and not the
Hi,
the read/write graphs in my relay's TorStatus.blutmagie.de page have
been broken for some time (flat-lined) but I assumed that was down to
my old software. However, I see that all the relays' pages are the
same. Is this data no longer available?
I had a quick look in the archives for an
57 matches
Mail list logo
