Hot answers tagged

4

To edit the group membership status and re-add yourself to the sudo group you must first access the encrypted, volume-managed file systems. The latter part is the same as for file recovery in such a situation. To summarize the sequence of necessary steps and link each one to more detailed instructions: Boot from a live DVD/USB an choose "Try Ubuntu". ...


2

The easiest and most fail safe way will be to save your files in password protected archive files, 'zip' being the most popular archive file format supporting such protection. This format is supported directly in most OS's including Ubuntu and Windows, without installing any other applications. If you want complete drive encryption you'll have to install a ...


2

The software you are mentioning isn't safer than the one built into Ubuntu. No need to purchase anything special. The software you are talking about uses "256-bit AES encryption" according to their website. You can have an encryption using the same algorithm using the "cryptsetup" on Ubuntu with a regular thumb drive, see for example: ...


2

This will be a bit of a simplification, but I'll try to go through the process of accessing a file on an encrypted filesystem. For example, let's say a the beginning of the encrypted filesystem there's a file table; let's say we want to read /foo.bar. So, the first thing we do is read the beginning of the partition, decrypt it, and look through it for the ...


2

How does AES / Rijndael Encryption in general work? This page has a fun A Stick Figure Guide to the Advanced Encryption Standard (AES) that looks easy to understand, though it looks to be 50+ images, for example these two: and It's far too much to duplicate it all here, but if you have to have an all-in-one image it's this one: Or, there's a ...


2

The processor uses dedicated instruction set. It is possible because of it, AES-NI. It enables fast encryption and decryption or you can say it cuts the overhead. It is fast because it is hardware implementation, as explained here. You can check about performance impacts here and they are worth it for added security.


2

I want to remove the decryption... I want to decrypt my drive so that i don't have to use dislocker tool every time I need to access my drive. Kind of like turning off bitlocker permanently. That's similar to re-formatting any drive with a new filesystem, but to keep the files there are a few more steps: Copy the files somewhere else (in this ...


2

The new hashing algorithm will be used only when creating new hashes. The old hashes in /etc/shadow will be still supported. All users would have to change the password to apply the new algorithm to their hashed password. Being able to rehash existing passwords would really beat the purpose.


2

It's a standard SATA drive. There should be no reason you can't. Hard drives don't come encrypted out of the box.


1

Boot from installation media and select "Try ubuntu". Open/decrypt with cryptsetup, Mount the local disk, chroot to it, and re-add yourself!


1

For completeness' sake, I post the solution we found during our conversation in the comments section as an answer: First of all, you are probably able to boot into your Linux system, you may just not be able to log in graphically, since graphical login usually tries to read/write in your home directory. You can still try to log in using a virtual console ...


1

As long as you ensure that non of the data on the encrypted partition is needed to enable a system boot you could just remove the reference to it from /etc/crypttab to stop it from being auto-mounted at boot. Alternatively you could leave the reference in place but add the noauto option. As for the swap the easiest solution here is just to have it be ...


1

The conflict has been caused by an invalid line in the /home/user/.gnupg/gpg.conf file. This particular line pinentry-program /usr/local/bin/pinentry-gtk-2 had been added by the user for Enigmail to work (troubleshooting item 'Resolving issues with GnuPG 2.x and gpg-agent') and had been worked like a charm for a long time. Apparently there must have been ...


1

After editing /etc/crypttab, run sudo dpkg-reconfigure lvm2 in a terminal.


1

Support for resizing LUKS partitions is being added right now to KDE Partition Manager. Grow support is already done in unreleased git versions and shrinking will be added soon. It will probably take a while until it reaches distributions and in particular Ubuntu but it will work at some point. Growing and shrinking LUKS in action: ...


1

I just ran into the same issue. What had happened is that the key was stored in the old format: cat /etc/ssh/ssh_host_rsa_key SSH PRIVATE KEY FILE FORMAT 1.1 <encoded private key here> However the newer sshd is expecting the newer base64 encoded keys. cat /etc/ssh/ssh_host_rsa_key -----BEGIN RSA PRIVATE KEY----- <base64 encoding here> ...



Only top voted, non community-wiki answers of a minimum length are eligible