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.
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.
Could you run sudo lshw -C network
and post the output for the wireless interface?
The ecology supports it then. S. variegatus would have been found near pine.
Possibly X. subtomentosus, based on the cracks on the cap. What kind of tree was it found next to?
We have those on I2P already, see tracker2.postman.i2p for example.
Was it found near birch? Possibly Leccinum scabrum.
You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.
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.
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).
The snowflake proxy acts as a bridge to the tor network at the entry side. If by repercussions you mean risk of exit-node traffic, there are none. It might cost a little bit of bandwidth.
Memory safety would be the main advantage.
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.