0v0
Memory safety would be the main advantage.
The bot missed the remaining 7 pages and the result of the benchmark:
“Overall it comes down to what workloads you are engaged in whether you may notice any performance difference when upgrading your Linux kernel (or otherwise being patched for Inception on your given OS) on an AMD Zen desktop or server. For the most part users are unlikely to notice anything drastic, aside from some sizable database performance hits in a few cases. It’s unfortunate seeing some of these regressions due to the Inception mitigation but ultimately is unlikely to really change the competitive standing of AMD’s latest wares on Linux. Most of the prior AMD CPU security mitigations have also not resulted in any performance degradation, so this Inception mitigation difference is a bit rare. It also was announced on the same day as Intel Downfall where there was again a sizable hit to Intel CPU performance.”
I occasionally experience the same thing. When this happens, it appears the jwt token is not sent with the initial request (thus appearing to be logged out), but it is sent with api requests on the same page (unread_count
, list
, etc.), so the cookie is not lost (document.cookie
also shows it). Sometimes refreshing again fixes it, but I haven’t yet found a good workaround. I’ll experiment a bit next time it happens.
I thought about torrents, but found no way to do that privately either.
You can torrent privately using I2P (It’s like Tor but peer-to-peer). The Java router comes with a pre-installed torrent client, accessible from the console. After installing and setting up your browser you can browse the main tracker at tracker2.postman.i2p.
I’m not on NixOS, but I have a decent working knowledge of Tor.
Not quite clear on what you’re trying to do, are you trying to run a relay, or just connecting to the Tor network and pointing your browser to the socks proxy?
Arti (the official Tor implementation in Rust) is not a complete replacement for the Tor C implementation yet. Hidden service support is disabled by default (due to the lack of a security feature that could allow guard discovery attacks), and bridges don’t work either. If you don’t understand Tor very well stick with the old router.
Here is a config template to run an obfs4 bridge, make changes as required:
BridgeRelay 1
# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ORPort TODO1
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:TODO2
# Local communication port between Tor and obfs4. Always set this to "auto".
# "Ext" means "extended", not "external". Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto
# Replace "" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo
# Pick a nickname that you like for your bridge. This is optional.
Nickname PickANickname
You can also use the reachability test to check if everything is configured correctly. If it is reachable and bootstrapping reaches 100% you should be set.
Set SocksPort
if you want to connect your browser (don’t confuse this with ORPort
). Default is localhost:9050.
Have you tried running tcpdump
/ wireshark
on another device in the network when this happened?