Activity for Blip of Consciousness
-
Blip of Consciousness posted a comment on discussion General Discussion
Mounir, you may or may not see this but it needs to be said regardless. I just wanted to take a moment to acknowledge the tremendous effort put forth by you into the VeraCrypt project. Upon reading the BSI security evaluation that recently came out, all I could think about was the countless hours and late nights (for 7 years!) you must have put in to continuously improve the program. VeraCrypt is obviously a passion project and your effort does not go unnoticed. Thank you Mounir. Thank you Enigma2Illusion...
-
Option to include VC portable when creating encrypted removable drives and auto-run VC portable upon drive mount, if possible. When I insert my bitlocker encrypted drive, I am greeted with a passphrase prompt. This ease of use would be a great benefit to the users of VC. An encrypted removable drive should be a self contained system that does not require the use of external programs to function.
-
It would be nice if there was a central, continuously updated webpage page that shows the Audit findings and if those finding have been corrected or not for whatever reason + the VC version that correction took place . That way the users could see the current versions attack vectors.
-
It would be nice if there was a central, updated webpage page that shows the Audit findings and if those finding have been corrected or not for whatever reason. That way the users could see the current versions attack vectors.
-
Option to include VC portable when creating encrypted removable drives and auto-run VC portable upon drive mount, if possible. When I insert my bitlocker encrypted drive, I am greeted with a passphrase prompt. This ease of use would be a great benefit to the users of VC. An encrypted removable drive should be a self contained system that does not require there use of extenal programs to function.
-
When I insert my bitlocker encrypted drive, I am greeted with a passphrase prompt. This ease of use would be a great benefit to the users of VC. An encrypted removable drive should be a self contained system that does not require there use of extenal programs to function.
-
I've been using VC exclusively with HDDs rather than flash media due to HDDs seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDDs rather than flash media due to HDDs seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDDs rather than flash media due to HDDs seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDD rather than flash media due to HDD seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDD rather than flash media due to HDD seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDD rather than flash media due to HDD seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with HDDs...
-
I've been using VC exclusively with HDD rather than flash media due to HDD seeming to be a more secure storage media compared to SSDs due to TRIM/Wear Leveling technologies inherant to to SSDs. I am curious as to whether or not SD cards are safe to use with VC (non-system whole drive encrypton use case). The idea is to encrypt the drive before any personal info is written to the drive (no sensitive info will be written to an unencrypted SD card at any time). Good or bad idea? Should I stick with...
-
Yes, I am using system encryption & you are correct that Fast Startup was causing the issue. I am now able to Shutdown normally now. I've seen the release notes that were provided when 1.24 came out, however, there is no meantion that Fast Startup must be disabled in order to Shutdown. It is not immediatly obvious (to me at least) of the connection. Perhaps the documentation should be updated for clarification? Also, disabling Fast Startup is 2 lines of code. Would it be possible to have VC disable...
-
Selecting Shutdown fails to shutdown system & returns to the windows login screen then to desktop as if Windows just started. Continuted attempts result in the same loop. Restart and Sleep seem to work normal. Machine: HP 15 running Win10 (fully updated as of 10/10/19) VC: 1.24 My tests (Shutdown = manually selecting shutdown button) After enabling RAM encryption & retarting OS: Shut Down (failed)>Shutdown (failed) > Hard Shutdown After disabling RAM encryption & retarting OS: Shutdown (success)>Boot...
-
Selecting Shutdown fails to shutdown system & returns to the windows login screen then to desktop as if Windows just started. Continuted attempts result in the same loop. Restart and Sleep seem to work normal. Machine: HP 15 running Win10 (fully updated as of 10/10/19) VC: 1.24 My tests (Shutdown = manually selecting shutdown button) After enabling RAM encryption & retarting OS: Shut Down (failed)>Shutdown (failed) > Hard Shutdown After disabling RAM encryption & retarting OS: Shutdown (success)>Boot...
-
Just letting others know that it look like 1.24 fixes the issue where windows would fail to start after a major windows update. Verified fixed on an HP laptop with multiple successfull restarts after installing 2019-10 Cumulative Update (KB4517389). Great job VC team. Keep up the great work!
-
It is very common and you are right. I am sure there are many people out there wondering whether or not their system truly has FDE. VC should explain why only the OS partition can be encrypted. The VC textbox should also include the ramifications and security comparisons vs whole drive encryption and steps the users can take to configure their system to enable whole drive encryption, if desired. The program has a fairly easy to understand interface execpt for this one issue. Fortunatly it's an easy...
-
Thank you for the update, Mounir. Hope you and your family are well. It's easy for people to forget that sometimes higher priorities come up in life that need to be addressed first. Anyway, glad to see this project is still active.
-
I can only speak about my situation, which may or may not be the same as yours. I have 2 HP laptops and the VC boot loader fails to start after major windows updates, even on 1.24 Beta 5. Fortunatly the fix is easy and does not require decrypting the drive. I boot into windows using the VC rescue media I then run a tool called VCFIXBOOT. This repairs the boot loader so that the rescue media is no longer required.. After the next major Windows update the boot loader will break again....repeat the...
-
Wondering the same thing. 1.24 has been in beta going on 9 months now. Hopefully the developers havent run into a roadblock.
-
I believe the default folder for the media is the Documents folder.
-
I think they changed the format, was ISO now .ZIP file. Either way it still should serve the same purpose. Burn ISO to CD/DVD and run it at startup.
-
look into running the chkdsk command to scan/fix any harddrive errors.
-
Not sure if its version 1809 specific or computer/manufacturer specific but VC breaks every major OS update for me. Here are the steps I take to get back into the system: 1) OBTAIN A USB FLASH DRIVE FORMATTED IN FAT/FAT32. 2) MOVE THE 'EFI' FOLDER FROM THE VERACRYPT RESCUE MEDIA FOLDER TO THE ROOT DIRECTORY OF THE FLASH DRIVE 3) RESTART COMPUTER, PRESS F9 & SELECT 'BOOT FROM EFI FILE'. 4) SELECT THE USB FLASH DRIVE > EFI > VERACRYPT > DCSBOOT.EFI 5) TYPE IN VERACRYPT PASSWORD 6) RUN VCFIXBOOT64/VCFIXBOOT32...
-
Thanks Mounir for clarifying this. Also, I just wanted to say thank you for all your hard work on the VC project. You are doing a great job.
-
I am trying to determine whether or not it is safe to store VC Rescue Media unencrypted. I would think that because the rescue media requires the user to input the password it does not, but I could be wrong.
-
Thank you, petitlou60. There is already a short term fix for this. It is a tool Mounir created called VcFixBoot. Unfortunately, it has to be ran every major windows update. You seem to have knowledge for the cause of this problem. Do you think that future versions of VC can fix this issue or will it always be a problem?
-
This message serves as a data point for the VeraCrypt team as well as other users who are currently having issues with windows updates breaking VeraCrypt resulting in ‘Preparing Automatic Repair’ message upon boot. Computer: HP 15-af175nr – running Windows 10 Home Computer configuration #1 VC Version: 1.23 Hotfix 2 Latest Windows Update: KB4512508 (August 2019) - fully updated as of 8/20/19 Behavior upon boot: Failed to boot - ‘Preparing Automatic Repair’ message after installing update VC rescue...
-
No idea man. You would think that if the pre-test worked than you'd be good to go. Could it be possible that you have a bad HD sector? Bad sectors could cause a VC drive not to unlock with the correct PW. Id use the recovery cd and try again.
-
Did you save the recovery disk/ISO file?
-
Only one way to find out... Install OS on windows, boot into OS and try to encrypt. You could also encrypt the drive and access via a live OS such as tails or win 10PE if you are concerned with data leaks.
-
Try to recover by using the recovery disk iso that was created when you encrypted the drive. HD corruption is a real thing and even a single bitflip can cause a drive to stay locked, even when the correct password is used. This happened to me. What I had to do was start from scratch. Run chkdisk on the drive, fix the errors, and start over if the recovery disk doesnt fix the problem.
-
Security is the priority, but be mindfull of the approx 10% overhead when enabling RAM encryption.
-
false sense of security unfortunatly.
-
Yes, you are correct. Thank you.
-
Good to get your opinion on OS only encryption. It was a question that I've always had about the possibility of data leaks to unencrypted partitions. Is there any plans to support UEFI in future releases of VC?
-
Good to get your opinion on OS only encryption. It was a question that I've always had about the possibility of data leaks to unencrypted partitions. Shouldnt you be able to encrypt whole drive if you turn on legacy support within BIOS? I tried this with my HP laptop and this option was still unavilable. msinfo32 still shows UEFI. Is there any plans to support UEFI in future releases of VC?
-
First off, I just wanted to thank Mounir & Enigma2Illusion for their outstanding commitment to the continuous improvement and support of Veracrypt over the years. It's evident that VC is a passion project and you two are making a great contribution to humanity through your work. When creating new volumes, there are sometimes options that are grayed out and unavailable for selection. Examples are "Hidden (sys. encryption)", "Encrypt the whole drive", and "Multi boot". It may be confusing for the user...
1
