FYI: My Tor node »TorMachine« (6A7551EEE18F78A9813096E82BF84F740D32B911)
will be shut down on 2024-12-31.
Sorry folks – but I'm too old for the job.
Good luck and all the best wishes for the future!
___
tor-relays mailing list -- tor-relays@lists.torpro
Example:
Fingerprint: 9D5A7A81BC6194555CE751F75FB196E4A3982CC5
This relay appears to be less than 2 weeks old.
Uptime
43 days 13 hours 30 minutes and 17 seconds
First Seen
2024-01-10 16:00:00 (14 days 2 hours 32 minutes and 41 seconds)
Last Restarted
2023-12-12 05:02:24
When will it be fixed?
Hi there,
today I found this warning in the log of my relay
(6A7551EEE18F78A9813096E82BF84F740D32B911):
Jun 03 04:04:33.000 [warn] Possible compression bomb; abandoning stream.
Jun 03 04:04:33.000 [warn] Unable to decompress HTTP body (tried
Zstandard compressed, on Directory connection (client r
Hi,
today I found this message in my Tor relay log:
Mar 17 14:26:17.000 [warn] Possible compression bomb; abandoning stream.
Mar 17 14:26:17.000 [warn] Unable to decompress HTTP body (tried
Zstandard compressed, on Directory connection (client reading) with
86.59.21.38:80).
What does it mean?
R
On 16.02.22 08:07, Martin Gebhardt wrote:
> In the attachment [2] you can find the config with %include.
There is no difference between attachment 1-torrc und 2-torrc.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.
On 23.11.21 17:01, Roger Dingledine wrote:
> I believe we are making a successful request to
> https://www.startpage.com/, and that is the reply that the webserver is
> sending us.
>
> That is, everything in the Tor side is working as expected, and startpage
> is sending a response that isn't wha
Hi,
in the last few days I noticed a curiosity with the Exitnode
4273E6D162ED2717A1CF4207A254004CD3F5307B:
Every time I call 'https://www.startpage.com', the URL in the Browser
changes to 'http://localhost/'.
Other browser: same effect.
Other sites - no problem.
Other Exitnodes - no problem with
Today, on https://www.youtube.com I got:
"An error occurred during a connection to www.youtube.com. Peer reports
it experienced an internal error. Error code:
SSL_ERROR_INTERNAL_ERROR_ALERT" (Browser Firefox)
With another browser (Chromium) same problem - no connect.
The exit node was 163.172.21
On 2014-11-18 18:46, Jeroen Massar wrote:
> Hence lets make a little list for clarity in order of "should at least do":
>
> - Use SSH Authentication
> - Disable Password Authentication
> - Use Fail2ban
> - Restrict on IP address (no need for fail2ban then)
Additionally - with ssh over hidden ser
On 2013-10-20 20:18, zwie...@quantentunnel.de wrote:
> Mine is a 3170. NEW: In my museum is still a 2170. Why not gonna try
> *this* ? I did and look at that! All works with just 9001 tcp and NO
> udp. This is good.
Fine. In the meantime my DSL-Router is replaced by a simple
DSL-Modem + Raspberry
On 2013-10-20 14:00, zwie...@quantentunnel.de wrote:
> Please find the listings http pastebin.com/43GZ1h5F
The relevant rules:
Chain INPUT (policy DROP 1062 packets, 82154 bytes)
pkts bytes target prot opt in out source
destination
14270 12M ACCEPT all -- *
On 2013-10-20 10:35, zwie...@quantentunnel.de wrote:
> Oct 20 07:32:08.290 [Notice] Now checking whether ORPort x.x.x.102:9001 is
> reachable... (this may take up to 20 minutes -- look for log messages
> indicating
> success)
> ...
> Oct 20 07:52:07.025 [Warning] Your server (x.x.x.x:9001) has
On 2013-10-13 06:42, Tor Operator wrote:
> My current iptables looks like this:
>
> # Generated by iptables-save v1.4.7 on Sat Oct 12 13:52:47 2013
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
> -A INPUT
On 2013-09-29 20:47, Konstantinos Asimakis wrote:
> Bridge on a dynamic IP? Does that even work?
Sure!
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-b
14 matches
Mail list logo
