Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
singlelogin.re still worked for me recently.
You can take the package from the Ubuntu PPA, which is generally updated quickly, and rebuild for Debian using the instructions here.
fn foo(x: i32) {
match x {
const { 3.pow(3) } => println!("three cubed"),
_ => {}
}
}
But it looks like inline_const_pat
is still unstable, only inline_const
in expression position is now stabilized.
It’s because it has to work in pattern contexts as well, which are not expressions.
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.
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.
Edit i2psnark.upbw.max
in i2psnark.config
(this can be in a number of locations based on install type and platform - just search for it).
Or you can remove the maxlength
and size
attributes from the text input, it will save just fine.
There is no central naming authority in I2P. All hostnames are local. (Naming and Address Book)
Therefore, if an url doesn’t work, it isn’t in your local address book.
You can add mappings yourself if you know the destination or b32 address, or make use of subscriptions. In this case, add http://i2p-projekt.i2p/hosts.txt and http://notbob.i2p/hosts.txt to your address book subscriptions, the latter contains the destination for mysu.i2p.
Try removing all the superfluous default routes.
Yes this is sane and one of the main use cases for encrypted lease sets. Encrypted lease sets make it impossible for unauthorized users to connect to your hidden services.
If you know beforehand that only one client needs to be able to connect, choose “DH” as a security strategy, and share the client’s key with the server. This article explains these concepts in detail.
If you don’t care about anonymity (given the 0-hop tunnels), you could also stick both hosts on an overlay network like Yggdrasil. This may or may not be more convenient / performant based on the number of services you want to expose.
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
.
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.
Redirector allows you to specify a pattern to do that.
Options:
torsocks
simply uses LD_PRELOAD, you could try to make this apply globally by adding the torsocks library to ld.so.preload. Just put the path returned bytorsocks show
in/etc/ld.so.preload
.