Quantcast
Channel: VeraCrypt
Viewing all 7620 articles
Browse latest View live

New Post: EFI booting HP laptop Help

$
0
0
I've managed to get the drive de-crypted.
Even with Medicat recovery CD, (great for getting into the system - if anyone that is not overly skilled in these areas is reading this.(like me!)) I wasn't able to give it the missing file.
I got to where it wasn't always asking for it, sometimes it just went into a loop of once authorised, went back to asking for the VC password.
The files seemed to be in the recovery part of the drive, but I couldn't get them into the boot section or if I did, they didn't stay there for start up.
editing the EFI files I wasn't able to figure out.

So for completion sake -
In my recovery disc, I replaced these
DcsBml.dcs
DcsBoot.efi
DcsCfg.dcs
DcsInt.dcs
DcsProp
Legacyspeakers.dcs
With the newest ones I could find on the net

(KEEP YOUR ORIGINAL svh_bak file)
(as said above, that has your encryption details on it)

Once the drive was decrypted, I used the downloaded from Windows windows recovery disc to boot with,
went into repair
Did the repair option
It copied the right EFI files from the recovery section and then all started up ok.

I probably now wait until the next VC version comes out before attempting this process again.
HP seems to have things set in a way that just wants to be very awkward with the UEFI process, I'm not sure if I want to risk the time lost again fixing this if I do it again and the same error occurs.

New Post: Cannot mount via command line, enter mount dir

New Post: Mac OSX 10.12 - can't mount VC volume (Mac Fuse issue ?)

$
0
0
Hi,

New MacBook Pro - Latest Sierra 10.12.4, VC 1.19, MacFuse 3.5.8.

No matter what I try to do I always get: hdiutil: attach failed - no mountable file system.

I tried with previously encrypted VC disk and I have the same issue. Conversely newly encrypted drives on my Mac do mount on older machines.

Only relevant info I see in log:
Detected missing constraints for <private>. It cannot be placed because there are not enough constraints to fully define the size and origin. Add the missing constraints, or set translatesAutoresizingMaskIntoConstraints=YES and constraints will be generated for you. If this view is laid out manually on macOS 10.12 and later, you may choose to not call [super layout] from your override. Set a breakpoint on DETECTED_MISSING_CONSTRAINTS to debug. This error will only be logged once.

New Post: Destroy key

$
0
0
What if the Destroy key opened a second but bogus file that looked similar to what was expected? That would work on the backup too, and divert further digging.

New Post: VeraCrypt Format.exe command line switch /keyfile (encrypt with keyfile)

$
0
0
The veracrypt.exe has the command line option /keyfile to mount a volume, but the VeraCrypt Format.exe does not have a command line option to create a new container using a keyfile.

Would it be complex to implement that feature?

Thank you for the great software!

Alex 1253

Commented Unassigned: Veracrypt bootloader defect [704]

$
0
0
I updated my veracrypt a few days ago to 1.19.

I just had a bluescreen which f*cked the bootloader.
All the data gone - I have to reinstall everything - thank you veracrypt developer.....

Stable Version... sure...

Comments: "All the data gone" No - just use your Rescue Disk and recover it!

New Post: Evil Maid attack message

$
0
0
I posted this once before and got no resolution, so I'm reposting.

I keep getting the "…bootloader fingerprint failed…"Evil Maid" attack…" message on boot. It only happens after I've travelled and logged onto the internet through a hotel wi-fi connection, and it always happens when I do. When I get home I use the rescue disk to restore the boot loader and key data, though I have to do that three or four times, and that eliminates it.

Most recently, the only internet access I made use of was looking up restaurants on Google Maps, and check e-mail with Microsoft Outlook.

Here's an interesting twist: my wife was traveling with me, and when I signed out so she could sign in and check her email, she didn't get the message. Over a period of several days, after finishing full boot, we repeatedly went back and forth, and when she signed in she got no such message, but every time I signed her out and signed back into my user account, I did get it.

Details are:
  1. Sony Vaio notebook.
  2. Windows 10 Pro, Version 1607 (64 bit)
  3. All software legit and properly licensed.
  4. Full disk encryption, no hidden OS
  5. Fully up-to-date Norton Security
  6. VeraCrypt 1.19 (64 bit)
This is clearly a false positive, and it is irritating.

Commented Unassigned: Veracrypt bootloader defect [704]

$
0
0
I updated my veracrypt a few days ago to 1.19.

I just had a bluescreen which f*cked the bootloader.
All the data gone - I have to reinstall everything - thank you veracrypt developer.....

Stable Version... sure...

Comments: And it begs the question. Why didn't you have your data backed up?

New Post: Hidden Volume Without Admin Privileges

$
0
0
I am using VeraCrypt on a Windows VM owned by someone else (as an exercise and not for actual security purposes). I can create regular volumes without problems, but when I attempt to create a Hidden Volume, it asks me for administrator credentials. Anyone know why this may be?

New Post: Code Plex shutting down Inquiry

$
0
0
Good to read you again, idrassi!

Created Unassigned: Issue of arm build: "Invalid characters encountered" after upgrade [707]

$
0
0
One or more of the following updates:
upgrade hostapd:armhf 1:2.5~armbian5.25+1 1:2.5~armbian5.27.170428+1
upgrade linux-dtb-next-sunxi:armhf 5.26 5.27.170427
upgrade linux-image-next-sunxi:armhf 5.26 5.27.170427

cause issues with the arm build.
When trying to mount a volume, after trying to decrypt veracrypt reports

"Invalid characters encountered"

after downgrading those three packages, the error is gone!

OS: armbian

New Post: uefi bios

$
0
0
Let me explain:
  1. I made UEFI support year ago. Project - disk cryptography services.
  2. Mounir published the result in version 1.18 to be audited.
  3. Version 1.19 contains audit result fixes. Audit team about the UEFI support: "It is actually one of the most important features added by VeraCrypt since the
    beginning of the project."
  4. Mounir stopped support the project since begging of this year.
  5. I published 1.20b2 patches 1,2 to fix problem with OS rescue disk and to show progress like: TPM 1.2 support (TPM 2.0 was done also but not published), multiple hidden volumes and many configuration options for pre-boot authorization
    https://sourceforge.net/projects/dc5/files/beta/
Result of year work: I can not find any funding for the project. Donation campaign produce nothing. (Note: I do not have access to VeraCrypt donations)
So => The project is not interesting.

New Post: Cannot mount via command line, enter mount dir

$
0
0
I'm using Veracrypt 1.19 on Linux Mint 18.1.

Four things:

a. Did you use to use Truecrypt? Veracrypt is much fussier (and rightly so - more secure against inadvertant typos) over correct syntax; it will fail if you don't get it absolutely right. So, always leave spaces between switches and arguments eg -p "supersecret", -k "". I got your command to work if I observed this rule.

b. Why use -k ""; if you are not using keyfiles, omit the -k switch altogether.

c. Does your cryptfile have a hidden volume? If not, omit --protect-hidden switch altogether.

d. Use the --non-interactive switch to stop being asked for the mount directory.

New Post: Linux Documentation

$
0
0
It's high time there was some Linux documentation on the Veracrypt website, rather than just an instruction to veracrypt -h from within Linux for command line help. Here's what that outputs:

Usage: veracrypt [--auto-mount <str>] [--backup-headers] [--background-task] [-C] [-c] [--create-keyfile] [--delete-token-keyfiles] [-d] [--display-password] [--encryption <str>] [--explore] [--export-token-keyfile] [--filesystem <str>] [-f] [--fs-options <str>] [--hash <str>] [-h] [--import-token-keyfiles] [-k <str>] [-l] [--list-token-keyfiles] [--load-preferences] [--mount] [-m <str>] [--new-hash <str>] [--new-keyfiles <str>] [--new-password <str>] [--new-pim <str>] [--non-interactive] [--stdin] [-p <str>] [--pim <str>] [--protect-hidden <str>] [--protection-hash <str>] [--protection-keyfiles <str>] [--protection-password <str>] [--protection-pim <str>] [--random-source <str>] [--restore-headers] [--save-preferences] [--quick] [--size <str>] [--slot <str>] [-tc] [--test] [-t] [--token-lib <str>] [--token-pin <str>] [-v] [--version] [--volume-properties] [--volume-type <str>] [Volume path] [Mount point]
--auto-mount=<str> Auto mount device-hosted/favorite volumes
--backup-headers Backup volume headers
--background-task Start Background Task
-C, --change Change password or keyfiles
-c, --create Create new volume
--create-keyfile Create new keyfile
--delete-token-keyfiles Delete security token keyfiles
-d, --dismount Dismount volume
--display-password Display password while typing
--encryption=<str> Encryption algorithm
--explore Open explorer window for mounted volume
--export-token-keyfile Export keyfile from security token
--filesystem=<str> Filesystem type
-f, --force Force mount/dismount/overwrite
--fs-options=<str> Filesystem mount options
--hash=<str> Hash algorithm
-h, --help Display detailed command line help
--import-token-keyfiles Import keyfiles to security token
-k, --keyfiles=<str> Keyfiles
-l, --list List mounted volumes
--list-token-keyfiles List security token keyfiles
--load-preferences Load user preferences
--mount Mount volume interactively
-m, --mount-options=<str> VeraCrypt volume mount options
--new-hash=<str> New hash algorithm
--new-keyfiles=<str> New keyfiles
--new-password=<str> New password
--new-pim=<str> New PIM
--non-interactive Do not interact with user
--stdin Read password from standard input
-p, --password=<str> Password
--pim=<str> PIM
--protect-hidden=<str> Protect hidden volume
--protection-hash=<str> Hash algorithm for protected hidden volume
--protection-keyfiles=<str> Keyfiles for protected hidden volume
--protection-password=<str> Password for protected hidden volume
--protection-pim=<str> PIM for protected hidden volume
--random-source=<str> Use file as source of random data
--restore-headers Restore volume headers
--save-preferences Save user preferences
--quick Enable quick format
--size=<str> Size in bytes
--slot=<str> Volume slot number
-tc, --truecrypt Enable TrueCrypt mode. Should be put first to avoid issues.
--test Test internal algorithms
-t, --text Use text user interface
--token-lib=<str> Security token library
--token-pin=<str> Security token PIN
-v, --verbose Enable verbose output
--version Display version information
--volume-properties Display volume properties
--volume-type=<str> Volume type

New Post: CodePlex shutting down: What is the plan for VeraCrypt?

$
0
0
Microsoft has announced that CodePlex will be shut down later in 2017.

What is the plan for VeraCrypt?

New Post: CodePlex shutting down: What is the plan for VeraCrypt?

New Post: Veracrypt cannot decrypt hard drive after moving to another system

$
0
0
Even when I didn' tget a tipp, here is my solution.

At Topic starter:
Perhaps your HDD was also a non-System drive, as System favorite? And you had entered your PW every time at System boot?
And perhaps you have also, after booting your OS, an None-EN-Keyboard-Language?

Then that could be also your solution... perhaps you have to Change Keyboard-Lang to EN for enter Password.(?)

Here comes "Why" and also the solution for my problem one post above:

Thanks for the Keyboard tip again, it solved the puzzle.
Before, I was sure my PW has to be entered in my local Keyboard-language. Why? -> Because I changed already my PW for c: SSD, and it's the same as for d: hdd system favorite.

The problem was, I didn't notice that TC is so clever, to change my keyboard-lang in Windows to EN on changing password of system drive c:. TC do the Keyboard-lang change without even make a pop up or notice, so I missed it. Because TC makes the Keyboard-lang change on system drive c: automatically, I was so sure about the Password also for d:
But in the end, I typed all the time the wrong password at password-change for d: hdd, because I never changed Keyboard-lang manually to EN for changing d: hdd Password-

Now I did the following, and everything worked:
  • remove d: as system favorite
  • reboot PC
  • changed PW for d: HDD with "select device" and select the before mounted partition. On PW change, set Keyboard-lang to "EN", of course for both PW, the old and the new one.
  • changed PW for c: SSD, TC makes the Keyboard-lang change to "EN" automatically, changed the PW to the same PW as the new d: Password. So both drives have the same PW on EN-Keyboard.
  • mounted d: again
  • added d: as system favorite again
  • reboot PC and could use new password
  • all runs fine
I am not sure if reboot and remove system favorite is needed, but like this it worked.

New Post: Windows 10: Command line task does not terminate.

$
0
0
For a long time, I have been using a script for my backups that mounts a volume using veracrypt.exe (in portable mode) with command line parameters:

.. some stuff
veracrypt.exe /q /v containerfilepath /l G /b /k keyfilepath
.. more stuff

Until recently, this has worked fine, but now, and sometimes only, the veracrypt.exe process does not terminate when the UI closes and the rest of my script is blocked. If I watch using Task Manager I see Veracrypt in the Apps list while the UI is showing and then it moves to the Background processes list. If I then do End Task on it, my script unblocks and completes normally.

There is no taskbar icon showing and the VeraCrypt Background Task is disabled in Preferences (as well as /q being specified in the command line).

Anyone have any insight on what might be happening here? I am ready to perform any experiments suggested.

New Post: Windows 10: Command line task does not terminate.

$
0
0
Did the problem start when your PC upgraded to Windows 10 Creators Edition?

Click on the Windows icon in the lower left of your screen and type "winver" without quotes then hit return.

Currently, Windows 10 Creator version is 1703 with OS build 15063-250.

New Post: Cannot decrypt system encrypted disk

$
0
0
I've encrypted (system encryption) my Samsung laptop today, with the pretest running fine.
So, I went ahead with the encryption and when I tried to decrypt the drive, it just booted into Windows automatic repair.

I've searched all over the Internet- trying to modify the EFI files, using beta rescue USB files etc. But none of them seems to work.

I just need to find a way to decrypt my drive so that I can pull out the files I was working on.

Here's what I already tried-
-Using a different rescue disk (Of course, it didn't work)
-Booting into a different OS (Linux Mint) and attempting to decrypt the disc from that OS
--> This led to a message that said my drive wasn't encrypted yet or something- apparently didn't work as well.

tl;dr: Can't seem to decrypt my encrypted system drive properly.

Also, the rescue USB menu seems to show up differently from other people- it shows like this

VeraCrypt rescue disk 1.19
d) Decrypt OS
m) Restore VeraCrypt loader to boot menu
z) Remove VeraCrypt loader from boot menu
etc......

Can anyone provide a solution?
Viewing all 7620 articles
Browse latest View live