This is to be expected, you get 100kB/s with iat-mode=2, and around
256-1024kB/s with iat-mode=1, however since most sites I load are just HTML/CSS
with little pictures, it is no big issue.
I would consider taking the speed penalty for more protection (as a research
paper also pointed out).
ty for a dubious and poorly understood
>
> privacy gain
>
> https://lists.torproject.org/pipermail/tor-relays/2021-February/019370.html
>
>
> I personally leave my bridges as they are, without iat_mode.
>
>
> Best,
>
> Fran
>
>
>
>
Regarding web-servers hosting Tor relays, it is much more likely for them to
sit behind a CDN such as Cloudflare for DoS protection and delivery
optimization.
Other services of course, however..
--- Original Message ---
xmrk2 via tor-relays schrieb am Sonntag, 11.
Juni 2023 um 1:46
Hello dear relay and bridge hosts,
recently a paper was published, describing a traffic confirmation attack called
DeepCorr, which works against Tor users and as such, also hidden services.
The attack allegedly had success rates of up to 96% percent.
It is being worked on and listed here as a
Hi,
while going through journalctl I noticed the following entries from my exit
relay and wanted to report this non-fatal assertion.
I also host a Guard relay on the same VM and IP, and it did not yet assert that
message.
The full assert() with the stack-trace is as follows:
> Dec 14
Hello Likogan (you did not specify a name, so I just took your domain name).
First, lets look at issue number one:
If your Tor Exit is using ~50% of the entire CPU (VM or dedicated server?)
while only routing 6 Mbps, then you are likely not using hardware AES
acceleration (aesni).
For
Please read the code, not only Tor's code, but also OpenSSL's code.
Yes, AES is not displayed as engine itself, however, it still does not seem to
use aes-ni instructions unless told to initialize engines via the code I
deducted.
If this proves anything, I ran an Exit Relay in 2013 before my
.
>
> I'll probably remove all limits for January and just see how much traffic
> gets transferred.
>
> ---
> Thanks,
> Dan
>
> On Thursday, December 21st, 2023 at 8:04 AM, George Hartley via tor-relays
> tor-relays@lists.torproject.org wrote:
>
>
>
>
any
security, performance or privacy implications, then please maybe just make it a
harmless information message.
Regards,
George
On Monday, December 18th, 2023 at 11:12 AM, trinity pointard
trinity.point...@gmail.com wrote:
> Hi,
>
> this looks related to TROVE-2023-007 /
> ht
- Is it possible to immediately remove my relay from relay search on Tor
Metrics?
No.
- If not, when will my relay be removed from the relay list?
Generally 7 days after your relay last uploaded it's descriptor.
Happy holidays,
George
On Sunday, December 24th, 2023 at 11:10 AM,
Hi Dan,
>1 - Is it better for the network if the relay is active 24/7, even if
>sometimes it's much slower?
Generally according to the relay requirements a relay is considered useful if
it can at least route 2MB/s or 16 MBit/s steadily.
However, I think you should get away with 1MB/s or 8
Also,
it should not nearly be as frequent, it happens maybe every 30-45 minutes on my
two relays (one guard, one exit).
Try running Tor natively (you can just move it to a native Linux installation,
by preserving the "`keys/ed25519_master_id_secret_key`" and
`"keys/secret_id_key`" in your Tor
Dear Jeff Blum,
> Yes, I am seeing something similar on 0.4.8.9 (and potentially earlier
> versions as well, not 100% sure when it started). I upgraded to 0.4.8.10
> today hoping it would go away, but I'm seeing it again. Watching in nyx
> (screenshot of bandwidth graph attached), reliably
Hello,
for about 3 months I have been hosting two Tor relays:
https://metrics.torproject.org/rs.html#details/AF42E6C77196A37F041A1A1E953E51B4656BDC1B
https://metrics.torproject.org/rs.html#details/7F7D1A5BE88FA7C9358955705AE7AFA61EEDA2B0
After doing system maintenance (mainly upgrading
Hi,
I think this started with release 0.4.8.10, but both of my Tor relays no longer
reload their config when doing for example:
- systemctl reload tor@exit
Here is the relevant part of the unit file:
> [Unit]Description=Anonymizing overlay network for TCP
> After=syslog.target
7 d a y s.
On Monday, January 8th, 2024 at 9:54 AM, 0tpcqovw--- via tor-relays
wrote:
> I think it's after 30 days it gets automatically removed.
> Malcolm
>
>
> On Mon, Dec 25, 2023, 15:25 nemeto via tor-relays
> wrote:
>
> > DuckDuckGo did not detect any trackers.
> >
> > Hi,
> >
)
Everything else seems fixed.
Regards,
George
On Thursday, January 11th, 2024 at 2:18 AM, George Hartley via tor-relays
wrote:
> Hello,
>
> for about 3 months I have been hosting two Tor relays:
>
> https://metrics.torproject.org/rs.html#details/AF42E6C77196A37F041A1A1E9
Hey there,
Debian offers unattended upgrades for specific packages:
https://wiki.debian.org/UnattendedUpgrades
If you follow this sites instructions carefully, then you don't have to worry
about updating Tor manually anymore (but you would want to if there is a
significant security issue that
18 matches
Mail list logo
