Tag Info

New answers tagged

0

Basically there are two stages to this. decrypting mounting the Logical volumes Assuming your drive is on sda5 (which is the Ubuntu default AFAIK but might be different) sudo cryptsetup luksOpen /dev/sda5 luks You are then promted for your password. Than do the LVM stuff sudo pvscan && sudo vgscan && sudo vgchange -a y Use lsblk ...


1

Solution: Old Wubi versions have bugs but i have found a solution from a forum post at ubuntuforums.org i can't find the same post but i have the links to patched files. This files are working. I tried the wubi from this link and worked. https://www.dropbox.com/sh/6uqomp8l1frcd1y/AAAhSCimTaYE-94egbmc1X_na?dl=0 Thanks to hakuna_matata


0

No, nobody will be able to access your encrypted data without you passphrase. This is the whole point of encrypting data.


0

I'm honestly not sure what you're asking, you seem to ask multiple questions. What I get is, is that you're asking wether someone with physical access to your PC, can access your encrypted data? If a person has physical access, and your PC is running, they can at the very least access the decrypted data from memory. If the PC is turned off, they will need ...


2

I am writing now from the machine that works exactly that way. First, you will need to put whole /boot folder on the dongle. Encrypt the disk with key file and put the keyfile into the boot dongle too. Edit /etc/crypttab, add this line sda2_crypt UUID=14-88 /dev/disk/by-uuid/88-14:/rootfs.key luks,keyscript=/lib/cryptsetup/scripts/passdev where ...


1

Your password issue is a problem of outdated Wubi versions. If it is your wish to use an old Wubi version that works without password issue, try lastest version for 12.04: http://releases.ubuntu.com/precise/wubi.exe In your case (Windows is not in UEFI mode) it should work.


0

It sounds like the key file that you are trying to use is at least 8 KiB, which exceeds cryptsetup's default maximum size. You can use the --new-keyfile-size <size_in_bytes> option to force cryptsetup to use the key, but I recommend using a random key with a smaller size, because a key that is larger than the master key of the LUKS volume offers no ...


0

How do you know it does not recognize swap? According to the right part of your screenshot the system does know there's swap. According to the memory stats in the left part of your screenshot you use about 57% of your memory so about 43% is still free. This is apparently enough so the system has no need to use swap right now.


1

Run sudo fdisk -l to find swap partition (i.e. /dev/sda6) Grab UUID in /etc/crypttab or sudo blkid for /dev/sda6 (replace device with your swap) Run sudo mkswap -U UUID /dev/sda6 (replace UUID and device with your swap) Append ,offset=1024 to the end of cryptswap1 line in /etc/crypttab Add "/dev/mapper/cryptswap1 none swap sw 0 0" to /etc/fstab Run sudo ...


1

The whole point of encryption is to make it impossible to access data without the passphrase. So there is no way to restore your data if you lost it.


2

You create an LUKS container on a partition or your whole SD card. I give you the GUI version: Open up Disks, choose your SD card, click on the wheel and choose Format. For Type, choose Crypted compatible with linux, enter a passphrase and choose Format. You will be asked for this passphrase when you mount your SD card. Don't forget it. Caution: You will ...


1

If your really just want to encrypt a directory, use encfs. You need a 2nd folder which is where you will work out of. In the 2nd folder, everything appears unencrypted while it is mounted. From the encfs manpage: encfs ~/.crypt ~/crypt The first time you will setup the password. Thereafter, you use the same command to unlock it. Files stored in ...


1

A.B. has already written a simple method to shred the volume. However, in case of encrypted volume, you can skip shredding and simply delete the volume as well (shredding takes time). rm -rf /path/to/volume


2

Remove the file with, eg: sudo shred -u /dev/disk/by-id/<your_filename> And as Terrance says in the comments: Better to take time to eliminate, then to be sorry in the future. from man shred shred - overwrite a file to hide its contents, and optionally delete it -n, --iterations=N overwrite N times instead of the default (3) -u, ...


0

You may want to try the following:Boot from a live CD/DVD/USB and then select the option to manually install Ubuntu. Now choose the correct options to mount the root partition to / and the home partition to /home. Make sure you DO NOT select the option to format those partitions, Now choose the option to mount the boot partition to /boot and now you DO ...


0

In case anyone has the same problem, vgimportclone is your savior.


2

Evidently, you ran ecryptfs-migrate-home, at the end of which, the following instructions were printed: ======================================================================== Some Important Notes! 1. The file encryption appears to have completed successfully, however, chris MUST LOGIN IMMEDIATELY, _BEFORE_THE_NEXT_REBOOT_, TO COMPLETE THE ...


3

CBC requires an IV: the very first block of data should be random. It is sent with the data so that the recipient has what they need to decrypt the message. The IV for CBC should be uniformly random and unpredictable. The openssl enc command creates an IV with 8 fixed bytes and 8 random bytes (it should be 16 random bytes). When you encrypt the same message ...


0

I had the very same problem when updating my laptop from 12.04.5 to 14.04.2. After fiddling around and (more or less willingly) deleting my "wrapped-passphrase" I used "ecryptfs-wrap-passphrase /home/my_user/.ecryptfs/wrapped-passphrase" with the mount-passphrase as "Passphrase to wrap:" and my login password as "Wrapping passphrase". After that login is ...


0

I think it might be an upstream issue. Linux Mint 17.2 (not 17.1) and Debian 8 are showing a CLI instead of GUI to decrypt system.


2

(I think you accidentally added the -d decryption option in the command in your question.) The encrypted files differ because of the random 64-bit cryptographic salt that OpenSSL generates and includes in each encrypted file by default. This can be disabled with the -nosalt option, but as the documentation in OpenSSL's man enc states, this is generally a ...


0

If you don't manage the loop device yourself, cryptsetup will automatically set up a loop device and close it when it is no longer needed. So there is no difference between the two; cryptsetup always works on the loop device. See man cryptsetup: NOTES ON LOOPBACK DEVICE USE Cryptsetup is usually used directly on a block device (disk partition or ...


0

Linux 4.1 comes with a new Ext4 feature to encrypt directories of a filesystem. Encryption keys are stored in the keyring. To get started, make sure you have enabled CONFIG_KEYS and CONFIG_EXT4_FS_ENCRYPTION kernel options and you have kernel 4.1 or higher. First of all, you need to update e2fsprogs to 1.43 from a git repository ...


3

This should work fine for you. The date command is all that is needed. alias cryptodoc="cd ~/Desktop/ && 7z a -pSome_Pass -r ~/Desktop/$(date +%Y%m%d)_Documents_Backup.7z ~/Documents/* 2>/dev/null" the command for date +%Y%m%d means, run date, then + means format, then %Y means YYYY, %m means MM and %d means DD. Having the $( ) around the ...


2

The easy way of doing this is to: remove the existing boot drive from your machine remove the the external drive from its enclosure and insert it into your machine Boot a LiveDVD install it as you want move the freshly installed HDD to the external enclosure. Then when you want to boot that, just go into your BIOS and boot from the external HDD. To keep ...


6

You're opening a compressed file. Vim in vi-mode doesn't support reading from compressed files, since this functionality is provided by plugins and plugins aren't enabled when in vi-mode (when compatible is set). Instead, try: vim /usr/share/doc/xdemorse/examples/xdemorserc.example.gz It might be the case that you have only vim-tiny installed. Install a ...


0

Caveat: I have not tried this myself What does the INITIAL encryption do in practice? For all data: - Read a bunch of the data - Process it in a special way - Write it back to disk Add the time to null out all free space (write zeroes). Answer: So the processing time should be similar to reading out all contents, then writing it back, with a ...


0

Try: gpg --encrypt --sign --armor -r person@email.com name_of_file you can add a second -r (recipient) flag to encrypt it for both you and the intended recipient, so that you can view the file as well.



Top 50 recent answers are included