There is, but if one gets through, they want us to forward it to this account that will be used to train, fine tune and improve the scanner for all mailboxes, as well as security training for employees.
Even though comments are very helpful, often it’s even enough to name variables and methods/functions really good. At least do that. You don’t want i, j and value. Believe me. You want rowCount, colCount and deliveryOption instead. You just may not know it now, but you will, when it has to be changed in a few months.
A good pasphrase helps the same for non-LUKS, but they still don’t have that specific weakness.
You can use cryptsetup without LUKS. However, something that starts to decrypt has to be unencryoted, so you can enter the password. Depending on how convenient it is for the user, it will leak some helpful info, like for example that the target is a valid file system that can be mounted or what cipher had been used.
to conceal this, you’d have to enter all it does manually in a shell/script without history. You could also add a number of bytes to skip as a sort of extra password and fill the start with random bytes, so it’s harder to find the start of the payload that is peobably a file system.
I mean that any attack gets more easy when you know, after it’s decrypted there are the bytes A, B and C at the locations X, Y and Z. It helps with brute force as well as hybrid attacks to find the master key.
LUKS does exactly have those specific Bytes at specific locations PLUS it has a marker that basically says “I am in this format and encrypted with this algorythm”.
If you use X and need to restart it, you can probably preemptively use XPRA to proxy your Xclients and move them to the new Xserver, except maybe for those that need low latency or DRM (e.g. games)
I don’t actually use it that much to input commands, but many scripts I made pop one up to show details of what’s happening, e.g. how opening the VPN connection is going, what crypto module it’s currently loading or how many more iterations a macro will do.
If you have a root account that allows logging in in text mode (no X no Wayland, no GUI), you would do that instead. These instructions are for that case. The home of root is /root , so it would not be affected.
Mount the new drive in an emty dir, if it isn’t already.
Make sure the other drives file system supports everything /home does.
Set the exact same permissions as /home/ in the new drives top level directory.
Add a line to fstab defining the other drive to be mounted automatically as /home .
Move the contents of /home over to the other drive.
Umount the other drive.
Enter just: mount /home
This should work without errors and if you peek inside, you should see user dirs and it should show up if you enter just: mount
No reboot necessary, you could just log out, switch to the GUI login and log in as regular user. After your next boot you will find out if you edited your fstab correctly to auto mount it. If not just log in as root in text mode again and fix it.
hyprland has this, but you have to configure it. It’s called Submaps. Some other tiling window managers/compositors (notion for example) have it too, but not to that extent. (notion can be enhanced by Lua scripting, tho.)
The idea is, after the first key of the sequence the meaning of a set of keys change. You could configure those to change the meanings again etc until you finally reach whatever depth you wanted and it performs an action.
However, be warned that hyprland is currently developed by very elitist people who like to support onky a very small set of distributions (primarily Arch btw) and have not much interest in other peoples Ubuntu shenanigens and the likes. It is extremely hard to install in Ubuntu and similar, requiring you to do minor edits to build scripts and source code in multiple languages and finding required library versions from build errors that do not mention them.
For a user: In Wayland programs are supposed to draw their own title bar. Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering. The terminology is different (compositor = window manager). Some niche new programs may only run on Wayland. Wayland hasn’t been adopted by BSD (AFAIK).
For a programners: Wayland has more modern, tidy code, but not all toolkits support it natively and few are easy. If you code exclusively for Wayland, a lot of users won’t use your program at the moment.