the warning disappeared.
What can I do?
The warning is reproted in tor-talk:
https:// lists.torproject.org/pipermail/tor-talk/2016-October/042425.html
--
Best regards, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https
mber on tor-talk, so that poster can provide
more details?
Might be.
--
Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Am 31.10.2016 um 23:40 schrieb Vinícius Zavam:
2016-10-19 2:30 GMT-03:00, teor :
On 19 Oct. 2016, at 16:25, Felix wrote:
Hi everybody
May be someone can help with this warning:
The security update (Tor v0.2.8.9 running on FreeBSD with Libevent
2.0.22-stable, OpenSSL LibreSSL 2.4.3 and
Am 01.11.2016 um 13:19 schrieb Vinícius Zavam:
2016-10-31 20:22 GMT-03:00, Felix :
Am 31.10.2016 um 23:40 schrieb Vinícius Zavam:
2016-10-19 2:30 GMT-03:00, teor :
On 19 Oct. 2016, at 16:25, Felix wrote:
Hi everybody
May be someone can help with this warning:
The security update
> Relays do not publish descriptors until their ORPort and DirPort are
reachable.
> What do I have to do - how to best set-up a decent strong firewall
on a freeBSD Exit?
If you run packet filter pf do you want to post the outputs to
'tor-relays' or better to 'lists.nycbug.org/pipermail/tor-bs
scrub in all
nat pass on $ext_if from $NET_JAIL to any -> $IP_PUB
rdr pass on $ext_if proto tcp from any to $IP_PUB port $PORT_TOR_JAIL ->
$IP_JAIL_TOR port $PORT_TOR_JAIL
That looks good.
There is no "pass out quick" or "pass out on" statement?
Sure, there is.
pass out on $ext_if proto { t
https:// consensus-health.torproject.org/
(observed 2017-01-03 16:00:00 and 2017-01-03 17:00:00)
shows
* dannenberg: Missing entirely from consensus
* faravahar: Missing Signature! Valid-after time of auth's displayed
consensus: 2017-01-03 15:00:00
* moria1: Sees only 2620 relays running
Is htt
Hi diffusae
> The only warning I have found close to it:
>
> "Jan 13 11:08:46.000 [warn] Your system clock just jumped 216 seconds
> forward; assuming established circuits no longer work"
>
> That could be due to the IPv4 autodetection? Maybe I should explicitly
> set the Address option in torrc?
Please check out
https://
metrics.torproject.org/userstats-relay-country.html?start=2015-10-22&end=2017-01-29&country=ae&events=off
vs
https://
metrics.torproject.org/userstats-relay-country.html?start=2015-10-22&end=2017-01-29&country=all&events=off
--
I this cool or not?
://
atlas.torproject.org/#details/6B7191639E179965FD694612C9B2C8FB4267B27D
--
Best regards, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
rsions please check ports/UPDATING,
libevent is 2.1.8 now.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
chapter 4.3.)
That's old school - how we saved bandwidth in ancient times :)
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Uhh. Wasn't there a transition to use self reported bw below some
threshold number ?
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
b (OR-type):
Tor 0.3.1.2-alpha (git-61625b8f26384a4a) running on
FreeBSD with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.5.3, Zlib 1.2.8,
Liblzma N/A, and Libzstd 1.2.0
--
(And why says the notice message "OpenSSL LibreSSL" ?)
Cheers, Felix
__
ep 2008) I find it
un-maintained, old and Tor does not configure for it:
checking for LZMA... no
configure: WARNING: Unable to find liblzma.
checking for ZSTD... yes
Is there a better lzma port ?
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@li
oth libraries available, it will use either one
> when appropriate.
>
> Of course, we can only use these compression formats when both sides
> support them.
Thanks. Clear to me. So 'Liblzma N/A' should not be an issue.
--
Cheers Felix
_
Zlib 1.2.8, Liblzma
5.2.2, and Libzstd 1.2.0.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[warn] Your computer is too slow to handle this many circuit creation
requests! Please consider using the MaxAdvertisedBandwidth config option
or choosing a more restricted exit policy.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproje
ate 20/10,overload )
# release the blockDIR after some hours
pfctl -t blockDIR -T expire 7200 # hourly cron job
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
9:37.000 [notice] Removed 4624 bytes by killing 115
circuits; 0 circuits remain alive. Also killed 1 non-linked directory
connections.
[] https://
lists.torproject.org/pipermail/tor-relays/2017-July/012624.html
- --
Cheers, Felix
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 27-Sep-17 um 08:19 schrieb teor:
>
>> On 27 Sep 2017, at 04:46, Felix
>> wrote:
>>
>> Sep 26 18:59:28.000 [notice] Removed 106528 bytes by killing
>> 14408 circuits; 0 circuits remain alive
>
> If you h
her too many statefull connects.
The ips might not be evil.
Heavy action can be you purge them or tcpdrop(8) before they hurt. Or
connection limit by ip per firewall.
--
Good luck and cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproje
ion.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
ing NAT; as far as I know,
> LeaseWeb does not use NAT, and Online.net only uses one-to-one NAT.
Good point. A general blocking rule should be smart enough to enable NAT
clients anyway ?
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@
ong queues. (This behavior is controlled by MaxMemInQueues.)
Dec 14 00:30:22.000 [notice] Removed 528 bytes by killing 509 circuits;
0 circuits remain alive. Also killed 0 non-linked directory connections.
--
Thanks and cheers, Felix
___
tor-relays mai
n the
remove/killing comes along.
> Another possibility is that Tor is failing to cleanup inactive circuits but
> with more information, we can eliminate options more easily.
What can I do ? The relay is still on with 3.4 GB. But circuits are
l is much lower than for a regular Tor
client.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
failed: Dec 21 16:35:33.000
> [warn] 17 connections died in state connect()ing with SSL state (No
> SSL object) Dec 21 16:35:33.000 [notice] Tor has successfully opened a
> circuit. Looks like client functionality is working. Dec 21
> 16:35:33.000 [notice] Bootstrapped 100%: Don
> If you are running a relay version >= 0.3.2.x (currently 281 relays in the
> network), please update as soon as you can with the latest tarball or latest
> git tag.
Update as well if HSDir is still present? The network might loose the
rare ones.
--
C
irst ACK and RTT)
If on Freebsd, is "mbuf clusters in use" (netstat -m) moderate ?
Do you get "kern.ipc.nmbclusters limit reached" in messages ?
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everybody
Is there an assembly or room for a concourse of Tor people?
Some coordinates like room number and utc would be apprechiated.
Hope to see you folks there :)
- --
Cheers, Felix
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
e to 120-210% during the flood.
I can not prove but because of outbound packet abuse letters from an
ISP I start thinking if this is an other measure to damage guard/hsdir
flags. Beside the enormous consumption of cpu resources.
I hope this helps.
[TAP 1] https://i.imgur.com/jDj3M5W.jpg
[NTO
.3.2.8-rc)
and there without the 'too slow to handle' warning:
17059168 circuits and 37961895 NTor in 3 hours (Freebsd, Jan 14th, Tor
0.3.2.8-rc)
Interesting here is the memory went up to 15GB where MaxMemInQueues was
set to 2GB.
--
Cheers, Felix
___
locking duration 1 day per ip.
Going to reduce fw after 24 hours step-by-step.
Thanks for the nice peace of software!
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
er instance are advised to disable it.
Thank you so much. I went crazy about sudden deaths
of relays too.
> CellStatistics can be turned off without restarting,
> via the control-channel command
> setconf CellStatistics=0
Without control-command one has to restart the se
50
FW: 100 connects per /32 ip, rate limited to 15 per sec.
Some hack to grab dos ips, their counts and defenses shows the well
known ones like a hand full new ones. But no surprises.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays
Thanks for looking into this
Am 14-Feb-18 um 00:25 schrieb teor:
>
>> On 14 Feb 2018, at 07:27, Felix wrote:
>>
> You can adjust these options without recompiling using the
> DoS* torrc options from the man page:
> https://gitweb.torproject.org/tor.git/tree/doc/tor.1.
it in like python :)
You can run a tor client and:
# grep "a.b.c.d" /var/db/tor/cached-consensus
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
.torproject.org/pipermail/tor-relays/2017-September/013041.html
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
It makes sense to rate limit (syn/sec) and connection limit Dirport
usage. I do this since years. The smaller a relay is the more it suffers
from excessive clients.
Can we get the DOS mitigation to perform it? As long as I observe this
issue it behaves like the Orport m
Hi
See: https bugs.debian.org/cgi-bin/bugreport.cgi?bug=773576
Debian will be fixed by 'apt-get update' and 'apt-get upgrade'.
dpkg.log tells if the fix is in place:
https security-tracker.debian.org/tracker/CVE-2014-9293 ...
Cheers!
___
tor-relays ma
$5B3B9A0EA1DC16F6348C57FCC83BBB43D1013F4A
I found Atlas was down between 21:30 ans 01:30 yesterday night.
Any ideas ?
Cheers, Felix
* http: jlve2y45zacpbz6s.onion/index.php
** https: consensus-health.torproject.org/consensus-health.html
___
tor-relays mailing list
tor
Hi
I'm happy to bring in the relay Doedel22
'8FA37B93397015B2BC5A525C908485260BE9F422'.
Best regards, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi
I stumbled over [1]. As I operate Doedel26 I checked DownloadExtraInfo
was default. After change in torrc to 1 and reload 'cached-extrainfo'
showed up in /var/db/tor/.
Can someone please advice how to deal with it ?
Best regards, Felix
[1] https://trac.torproject.org/projects/
d the first OR Port to :443 and the second to :8080. Both at the same
'eth' interface?
Both OR Ports are based on the same IP so they would be the same family
member.
Thanks for your answer. My response might have some delay. Sorry for
that.
would be a part of the
sender chain.
Felix
==-- - - - - - - - - - - --==
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)
mQENBFL/5VoBCAC8l2gGmuy2hZf866dDkwzOvMkyJlfnFZU6T5LWe4uPIx0a8R1U
cmj
d 'apt-get update' and 'apt-get upgrade'.
1.0.1e-2+deb7u5 should be good for Wheezy.
( Deleted keys, restarted tor, receive a new fingerprint and stand back
in line for new flags - but we are safe )
Felix
==-- - - - - - - - - - - --==
-BEGIN
Am Wed, 8 Feb 2023 00:08:39 +0100
schrieb nusenu :
Hi
> multi-instance tor relay
Can you please describe what that is? Is it a server with multiple
relays, each with it's own fingerprint? Or is it a relay with one
fingerprint and with multiple tor daemons that are synced by some magic?
pgp4ea
Hi
> Thanks for the reply. What would be a reasonable per-ip rate limit
> (connections per second) for a Tor middle relay?
On _Freebsd_ the following pf settings apply for running tor in a Jail:
table persist
MAXSRCCONN = "50"
MAXSRCCONNRATE = "5/5"
nat on $IFEXT inet from $IPTOR1 to a
Hi
> 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 reading)
> with 199.58.81.140:80).
We see the compression bomb warning from time to time
The ad
> Daniel Nikoloski
Hi Daniel
Not sure if that already has been answered. I don't use Kubernetes cluster but
I find this one interesting:
> > Address 38.242.233.101
> > ORPort 9001 NoAdvertise IPv4Only
> > ORPort 32150 NoListen IPv4Only
I believe the Tor server service will publish port 32150 bu
Authority?
--
Cheers, Felix
pgpJNICSpRZmK.pgp
Description: Digitale Signatur von OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
, but I have no clue what this might be.
Thank you for tracing this.
[1] https://nusenu.github.io/OrNetStats/
[2]
https://metrics.torproject.org/rs.html#details/B771AA877687F88E6F1CA5354756DF6C8A7B6B24
[3] http://185.220.101.32:10032/tor/extra/authority
--
Cheers, Felix
__
ir and Valid flags.
>
...
>
> Livak
Thanks for engaging and doing.
Did you consider to reduce your exit policy a bit like:
https://www.torproject.org/docs/faq.html.en#DefaultExitPorts
or what you can find in the history of this list?
--
Cheers, Felix
___
the entry
"Self-testing indicates your DirPort is reachable from the outside.
Excellent." Same for Orport. If you dont't need socks you can change it
to .
I hope I got you right. Good luck!
[] https://www.torproject.org/docs/tor-manual.html.en
--
Cheers, Felix
__
10,0.3.4.1-alpha,0.3.4.2-alpha,0.3.4.3-alpha,0.3.4.4-rc,0.3.4.5-rc,0.3.4.6-rc,0.3.4.7-rc,0.3.4.8,0.3.5.1-alpha
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Tyler
Am 12.10.2018 um 14:41 schrieb Tyler Durden:
> Our two exit nodes "chulak" and "aurora" will be terminated by the end
> of this month.
They were active for how long - forever? Chapeau!
--
Cheers, Felix
___
tor-rela
e file /var/log/tor/notices.log
RunAsDaemon 1
ORPORT 9001
DirPort 9030
ExitPolicy reject *.*
Nickname Lebowski1
RelayBandwidthRate 200 KB
RelayBandwidthBurst 400KB
-> ORPort 9001
PS: *Lebowski1* how cool!
--
Cheers, Felix
___
tor-relays mailing
drwx-- 2 _tor _tor - date/time keys
# ls -alo /var/db/tor/keys/
-rw--- 1 _tor _tor - date/time secret_onion_key
... more files ...
chown can heal it:
# chown -R _tor:_tor /var/db/tor
# chown -R _tor:_tor /var/db/tor/keys
I hope I got your points.
Please check bef
t-45028085ea188baf) running
on FreeBSD with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.7.4, Zlib
1.2.11, Liblzma 5.2.3, and Libzstd 1.3.5.
...
Oct 28 14:35:53.000 [notice] Bootstrapped 0%: Starting
Oct 28 14:35:55.000 [warn] parse error: Annotations mixed with keywords
Oct 28 14:35:55.000 [warn] Unparseable mi
d ips? The new ips aren't in any
fallback_dirs.inc's and [2] shows no fallback flag.
Would thereby [1] look better than it is?
[1] https://consensus-health.torproject.org/consensus-health.html
[2]
https://metrics.torproject.org/rs.html#details/F9246DEF2B653807236DA134F2AEAB103D58ABFE
--
4766
Ah, great! This makes sense. It's a transient to the list update.
> https://trac.torproject.org/projects/tor/ticket/24803
The upcoming one seems to be:
https://trac.torproject.org/projects/tor/ticket/28795
--
Cheers, Felix
___
tor-r
e 0
RelayBandwidthBurst 0
HardwareAccel 1
AccelName dynamic
Log info file /var/log/tor/info
--
Cheers from 35c3 , Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
end up in a well used server :)
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Am 31.01.2019 um 14:19 schrieb Felix:
Hi everybody
Circuit storms observed of up to 100k and 250k per relay for over hours.
Consumed BW rises by about 10%. Number of stateful server connections is
higher. Using Tor 356 to 401.
Anybody else observes that?
Switching to some paranoid server
B29CBA9F752864A0259E
A2E6BB5C391CD46B38C55B4329C35304540771F1
B86137AE9681701901C6720E55C16805B46BD8E3
3) Not normal:
https://metrics.torproject.org/hidserv-rend-relayed-cells.html?start=2017-01-01
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.
ectory and make sure the
filesystem permissions
are set properly and you should be fine.
And don't forget the fingerprint file :)
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/m
e and everything is like it should be. So please let me improve my
post like:
And forget the fingerprint file :)
Thanks and a nice weekend for everybody
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
A8
[3]
https://metrics.torproject.org/rs.html#search/family:1AE039EE0B11DB79E4B4B29CBA9F752864A0259E
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
wonder about the number of relays affected, meaning lost their Guard flags
around 15th of August and didn't get it back till today?
[1] me :
https://metrics.torproject.org/rs.html#details/63BF46A63F9C21FD315CD061B3EAA3EB05283A0A
[2] Felix:
https:
Am 2019-09-21 um 4:11 PM schrieb Toralf Förster:
On 9/16/19 9:19 PM, Felix wrote:
The sbws bandwidth authorities now can measure the bandwidth of the relay.
Can somebody confirm my observation or has prove (please no speculations).
I upgraded LibreSSL from 2.9.2 to 3.0.0 here at a stable
L 1.0.2s
9F5068310818ED7C70B0BC4087AB55CB12CB4377 Tor 0.4.1.6, LibreSSL 3.0.0
8FA37B93397015B2BC5A525C908485260BE9F422 Tor 0.4.1.5, OpenSSL 1.0.2t
suffering:
ED7F2BE5D2AC7FCF821A909E2486FFFB95D65272 Tor 0.4.1.3-alpha, LibreSSL 2.9.2
I hope that helps. Please tell me how I can support.
--
Cheer
vihay/hayes10__google_delay_based_tcp_conges_contr.pdf
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Exit
my fingerprint
You need to have the DirPort active. If the DirPort is on a
browser readable port (ie 80) you can browse, wget or curl
the relay_address:port and see if the daemon runs.
Have fun with your relays and stay healthy!
--
Cheers, Felix
__
.
It is helpful if you post the fingerprint and torrc file here.
Thanks for working hard to get the relay run.
Good luck!
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
e same way and finally relax DOS settings.
When ever the relay(s) become unstable go one step back.
This is a recommendation but there might better ways to go.
Good luck!
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
ard. I hear you.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[4]
https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
Cheers, Felix
__
0.0%50 98.4 98.4 98.0 100.3 0.5
Relays at other hosting locations choose for different routes and
longclaw sees them perfectly equal. It*s a case by case.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
h
eDesc) 0.4.4.5 =?=
May-be the operators updated and are now in the same floating position?
May-be this is super normal and came to my attention by surprise?
Anyways, I let everthing run for a day or so. Time can heal.
--
Cheers, Felix
___
tor-relays mail
S: We had the same trouble with Libressl 292 when 28x worked well and
30x too.
PPS: Is that a good reason to stay away from automated updates? Ok,
Libressl 321 is -devel
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproj
cause an issue with some Tor auths.
Libressl 3.2.2 is/was devel and sits as well in non-devel, so we can not
switch back this time :( .
[0] https://gitlab.torproject.org/tpo/core/tor/-/issues/40128
[1] https://svnweb.freebsd.org/ports/head/security/libressl/
--
Cheers, Felix
le, exit, entry)
Relays received shorter probes than bridges which were probed over about
5 hours. As well bridges that are announced (public) but didn't had any
'unique clients' so far.
--
Cheers, Felix
___
tor-relays mailing list
tor-rel
16-01-01&country=th
https://metrics.torproject.org/userstats-bridge-country.html?start=2016-01-01&country=th
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
?
I don't use OutboundBindAddress but given the name
"outbound-bind-address" the outbound traffic has to bind to a public IP.
And 192.168/16 is not public.
For what it's worth.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@
raffic during bursts from personal traffic pipes on Linux
> or BSD systems?
On BSD you could investigate in pf-altq and define customized queues.
But that will impact the bandwidth measurements and the consensus for
your relay.
--
Cheers, Felix
___
t
orks is:
http://relayip:dirport/tor/status-vote/current/consensus.z
Am I missing something and is everything good? A glitch?
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
e of "text/plain".
:: No bridge fingerprints ::
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
und timing
will be handled accordingly.
--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Dear All
The last days on this list were stunning, to say the least. I'm going to
unsubscribe today and i will decide tomorrow if i shut down all my relays.
We experience all kinds of attacks against privacy and our relays.
Let's stay together.
--
Che
:57 PM, Felix wrote:
Please somebody can _confirm_ this thing?
Much more worse:
The relay here under a hardened Gentoo Linux with LibreSSL 3.2.1 has only 50%
of the amount of the conenctions as with 3.2.0 at all - and the TCP traffic
dropped down by nearly 100%.
I recompiled Tor to ensure
Hi
Since all of my exit nodes are within the same /16 - would I have to run
bridges on newly acquired IPv4 space?--
A bridge has no `family´. An entity running bridge and exit generates an
end-to-end situation and might not be what we want.
Cheers, Felix
, forum, and matrix. Eventually the bridges will go
away too.
Merci vilmal and herzlichen glückwunsch!
Jonas
So sad to read what you posted. Tor seems to be a not unimportant part
of your digital life. Maybe things calm down over time.
--
Cheers, Felix
the max
conn per ip rate was above my applied max threshold. The notice level
DoS mitigation entry remained untouched while sitting behind the pf.
Beautiful!
--
Cheers Felix
pgp1I4_GKArH1.pgp
Description: Digitale Signatur von OpenPGP
___
tor-relays
Hi all
I found a message in the logs:
Apr 16 15:07:46.000 [warn] Received a bad CERTS cell: Link certificate
does not match TLS certificate
--
Cheers Felix
pgpz8Afm4HlbY.pgp
Description: Digitale Signatur von OpenPGP
___
tor-relays mailing list
tor
sing the full list of tor nodes and indiscriminately
> blocking everything
Yup, agree
Do you have IPv6 available for your office traffic? While you use IP4
for the relay. If you route email and browser along IPv6 you could
resolve the issue.
All the best!
--
Cheers Felix
pgptH6l_GO0WQ.pgp
De
rsion of Tor (0.4.7.8) is newer
than any recommended version, according to the directory authorities.
--
Cheers Felix
pgpKDS2ek1doi.pgp
Description: Digitale Signatur von OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproje
e for your
domain and/or fail SPF checks. Most of the "big" email companies seem to
respect DMARC now. See http://www.dmarc.org for details.
felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/
you are probably as safe as with key
based logins.
BR
Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
1 - 100 of 118 matches
Mail list logo
