Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don’t do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.
Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don’t do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.
Try removing all the superfluous default routes.
I think glider can do this, with -strategy rr
(Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn’t present a socks5 interface itself (it uses LD_PRELOAD
, so it won’t work everywhere).
Argon2id (cryptsetup default) and Argon2i PBKDFs are not supported (GRUB bug #59409), only PBKDF2 is.
There is this patch, although I have not tested it myself. There is always cryptsetup luksAddKey --pbkdf pbkdf2
.
Consider the string abc
. From the end, moving backwards, when does it match \w+
, and what does it match? When it reaches c
, it matches c
. And from the front, moving forwards? When it reaches a
, it matches abc
. This is why it acts differently.
The regexp itself always looks forward, the BACKWARD argument just determines which direction the point should move after a match.
Because once it hits the ultimate character of a word, \w+
matches that (single) character, next time it matches the penultimate character, etc. You’d need \W\w+
to make it look far enough back to the beginning of the word.
This seems right and exactly the way I’ve set it up. On subvolid=5 I have subvolumes and
@home
, in /etc/fstab
I mount /
as subvol=@
, and /home
as subvol=@home
.
https://stackoverflow.com/questions/10602504/how-does-user-js-work-in-firefox-in-detail:
It just looks like a JavaScript file. Once upon a time in Netscape 3 and maybe 4 it actually was, but now it’s just a file with a .js extension and a very restricted syntax that’s parsed by a separate (non-JS) parser and not executed in any way.
Could you run sudo lshw -C network
and post the output for the wireless interface?
Funny enough I arrive at this the most when I play the Triassic and my opponent goes for a Cretaceous game structure.
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.
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.
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.
But you can do this.
Indeed. This works because direct connections to the tor network are easily censored, but WebRTC is not (not without a lot of collateral damage at least).
You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.