Activity for Mounir IDRASSI
-
Mounir IDRASSI posted a comment on discussion General Discussion
For the record, there is indeed a bug in macOS Sequoia regarding exFAT volumes and disks and it is not specific to VeraCrypt. It has been reported to Apple since last year but no fix has been released: https://discussions.apple.com/thread/255188289?sortBy=rank. So, Apple officially doesn't seem to care about this and the only solution is to create new exFAT volumes on macOS Sequoia. Additionally, this article provides more details on the issue: https://appleinsider.com/articles/24/04/03/external-drive-support-in-macos-sonoma-is-partially-broken-and-its-probably-apples-fault....
-
@dvorak123: The error message indicates that the filesystem of your volume is not supported by macOS. What filesystem do you use for this volume? If you upgraded to Sequoia from a previous macOS version, ensure that any third-party product for non-native filesystems is also upgraded to ensure that it is working properly. Another possibility is that the volume has been corrupted somehow, but this cannot be caused by the upgrade to Sequoia.
-
Linux: Add Fedora as supported distribution in CMakeLists.txt
-
I have just installed macOS Sequoia on an Apple M1 machine and VeraCrypt 1.26.14 works correctly with FUSE-T. (FUSE-T is recommended for Apple Silicon due to issues affecting the installation of macFUSE on these machines.) @tedpoe: macFUSE 4.8.0, which was released in June, added support for macOS Sequoia, so it looks like you are using an old version. As I mentioned above, if you are using an Apple Silicon machine (M1/M2/M3), a better alternative is to use FUSE-T and install the FUSE-T version of...
-
Windows: Fix EFI configuration editor various issues
-
@bkev: Now I understand what is happening. The file ./src/common/cmdline.cpp is from wxWidgets and it is complaining about a missing switch. The FindOptionByAnyName function is part of the wxWidgets code. The GitHub build action uses a static build of wxWidgets from the 3.2.5 source and this assert is not triggered there. However, the assert is triggered when building against the version of wxWidgets included with Ubuntu. There was indeed a section of the code that queried for the --allow-screencapture...
-
Linux: fix assert by wxWidgets library included in Ubuntu.
-
@bkev: It looks like the error you're encountering is referencing a file that doesn't exist in the VeraCrypt codebase. Specifically there is no ./src/common/cmdline.cpp file and the actual ./src/Common/CmdLine.c file is only 184 lines long. Additionally, the function FindOptionByAnyName() mentioned in the error does not exist in the VeraCrypt source code. This suggests that the code you're working with might be a modified version of VeraCrypt, not the original. I have previously set up an automatic...
-
Windows: Simplify error message related to IsEfiBoot since it always fail with ERROR_INVALID_FUNCTION
-
macOS: fix regression in build script that caused it to ignore fuset switch
-
macOS: restrict --allow-screencapture switch to macOS only since screen protection doesn't work on Linux
-
Add Option to Enable/Disable Screen Capture (#1418)
-
Windows: Fix failed EFI detection on some PCs where BootOrder variable is not defined.
-
macOS: enhance macOS build script(allow local build, specify wxWidgets version, control packaging)
-
Update Language.sv.xml (#1416)
-
Since the cache needs to be wiped after the mount is performed, you will need to run this command in a separate execution once the mount is complete.
-
You can wipe the password cache using the command line: VeraCrypt.exe /wipecache /q To be sure, add this command at the end of your mount script to ensure that no password is cached.
-
The temporary cache setting only applies when mounting favorite volumes simultaneously and it is cleared once the operation is complete. Therefore, this cannot be the issue. Did you check if the 'Wipe Cache' button was enabled in the VeraCrypt UI? This would indicate that your password was somehow cached. Unless you accidentally ticked the 'Cache passwords and keyfiles in memory' checkbox in the password dialog, I don't see how this could have happened.
-
exFAT also supports files larger than 4GB and it definitely should appear in VeraCrypt list of compatible filesystems . I tested again with 4GB option and exFAT is there. can you please run the command "mkfs.exfat" in Terminal? It should display help message. VeraCrypt uses mkfs.exfat so it should be available in order to be displayed in the UI list. Did you reinstall exfatprogs package?
-
I have installed Pop!_OS in a VM (a very nice distribution by the way, user-friendly, I wasn't aware of it before). After that, I installed exFAT tools since they are missing by default: sudo apt install exfatprogs Then, I downloaded the VeraCrypt GUI package for Ubuntu 22.04 (since Pop!_OS is based on it), and I created a 1 GiB file container with some data inside (I explicitly selected exFAT in the wizard). Next, I transferred this file container to my Mac running macOS Sonoma and used VeraCrypt...
-
What filesystem did you choose when creating the volume on Linux? To ensure compatibility across all operating systems, you need to select a filesystem that is widely supported. The best choice today is exFAT, or even FAT if your volume is small.
-
It looks like you didn't mark the VeraCrypt public key as trusted. While the signature is valid (as indicated by "Good signature"), GPG is warning you that the key is not certified with a trusted signature, meaning you haven't explicitly trusted the VeraCrypt public key yet. The VeraCrypt documentation mentions this step here but it doesn't provide detailed commands for doing so. On Ubuntu, you can trust the key by following these steps: Sign the VeraCrypt key with your own key to mark it as trusted:...
-
@xykar: I think you may have missed specifying ACCEPTLICENSE=YES in the msiexec command line. Here is an example of a command line that runs VeraCrypt in silent mode: msiexec.exe /i "VeraCrypt_Setup_x64_1.26.15.msi" /qn ACCEPTLICENSE=YES If a Windows reboot is required to complete the installation, it will happen automatically. If you want to disable the automatic reboot in silent mode, you need to add REBOOT=ReallySuppress, as shown below: msiexec.exe /i "VeraCrypt_Setup_x64_1.26.15.msi" /qn ACCEPTLICENSE=YES...
-
@an1: Thank you for reporting the issue and fixing it. After checking the history changes, this issue was introduced after merging translation provided by a contributor on Github; https://github.com/veracrypt/VeraCrypt/pull/1270 Clearly he did some automatic changes on certain fields and this created the problem. What is strange is that I use a script to check the validity of XML files and it should have caught such issue since it is a simple wrong escape sequence. I will need to review the script...
-
Linux/macOS: Fix missing define that was causing compilation error
-
Translations: Fix wrong escape sequences in Swedish translation (fixed by @an1 on Sourceforge)
-
Windows: Add support for x86 and x64 build for driver and binaries using Visual Studio 2019
-
Windows: use wcstok_s instead of wcstok for more secure parsing of directory path
-
Well... the naïve approach doesn't work! Now I remember the issues linked to the volume GUID, which is managed by the Windows Mount Manager. There is a missing piece in the puzzle to allow bypassing the initial full mount to get the volume GUID. This will need some work.
-
@petitlou60: The issue you're encountering is not specific to VeraCrypt but rather related to the Windows MountManager cache. If the MountManager cache contains the GUID of the volume, the mountvol command will work when the VeraCrypt volume is mounted using the noattach option. Otherwise, you will need to mount the volume normally once, dismount it, and then mount it again using the noattach option. Six years ago, a user (@adriankit) shared a script that automates this process. You can find it here:...
-
@ggiunta: I have added the missing CONTRIBUTING.md. It is fairly generic, similar to those used in many other projects.
-
@ggiunta: Thank you for your feedback. I will go with your choices, as you have more practical experience on this subject than I do. Regarding protection against spam/bots, using existing libraries that are battle-tested makes more sense than reinventing the wheel and ending up with an inefficient solution. I have created a Git repository for future development: https://github.com/veracrypt/VeraCrypt-CrashCollector You can fork it and create Pull Requests for the various stages of development. Pull...
-
Add Project README.md and Apache 2 LICENSE
-
VeraCrypt provides native ARM64 support for Windows. It works on Surface Laptops and other ARM64-based devices without the need for emulation. By the way, emulation doesn’t work for Windows drivers so I had to port the VeraCrypt driver to ARM64 to make it compatible.
-
@userhd: Thanks for providing the details. As I suspected, this appears to be a heuristic-based detection which can sometimes lead to false positives. In my experience, it's not uncommon for less established antivirus engines to report higher rates of false positives when using heuristic analysis compared to major AV solutions. Nonetheless, it's always a good idea to cross-check with other engines for confirmation.
-
@slapshot @enigma2illusion: This is a tricky situation. In portable mode, while there’s technically no installation, VeraCrypt still loads its driver into the Windows kernel using the portable binaries to enable volume mounting. However, in many cases, the driver remains loaded, even after the portable instance is closed. This creates an issue when you try to run a new set of binaries since the system will default to using the already loaded driver which may not be compatible with the new binaries....
-
@enigma2illusion: I try to stay organized to optimize my time and keep track of all necessary tasks but I'm not as efficient or as fast as I was 11 years ago. I've slowed down which explains the various small issues that pop up here and there.
-
Thanks @userhd for the information. Could you please share more details about the error reported by AV 360 TS? VirusTotal doesn't show any positive detections: https://www.virustotal.com/gui/file/bc569a7876587ee139254ccd058493bed1d8a5efe3cd6b4578a2a4125950ae86 Unfortunately, false positives often occur with new releases. This is typically resolved within a few weeks once people report them to the affected vendor.
-
Indeed, my bad! I have just update Sourceforge link to latest release. Sorry for the misunderstanding.
-
The VeraCrypt homepage was updated yesterday to reflect the 1.26.15 release, so it's strange that you're not seeing it. I think your browser is showing a cached version of the homepage. Try clearing your browser cache.
-
@ggiunta: Here are my answers: Hosting: VeraCrypt website is hosted on a dedicated server, and the crash reporting will be hosted on the same server. This ensures easy management and integration with existing infrastructure. Authentication/Authorization: There should be a mechanism to define the administrator credentials during the first installation. Afterward, the administrator can add extra accounts. A simple authentication mechanism based on MySQL or SQLite, stored securely on the server, is...
-
@ggiunta: Here are my answers: Hosting: VeraCrypt website is hosted on a dedicated server, and the crash reporting will be hosted on the same server. This ensures easy management and integration with existing infrastructure. Authentication/Authorization: There should be a mechanism to define the administrator credentials during the first installation. Afterward, the administrator can add extra accounts. A simple authentication mechanism based on MySQL or SQLite, stored securely on the server, is...
-
@ggiunta: Here are my answers: Hosting: VeraCrypt website is hosted on a dedicated server, and the crash reporting will be hosted on the same server. This ensures easy management and integration with existing infrastructure. Authentication/Authorization: There should be a mechanism to define the administrator credentials during the first installation. Afterward, the administrator can add extra accounts. A simple authentication mechanism based on MySQL or SQLite, stored securely on the server, is...
-
I have identified the cause of the issue: an old bug in the function responsible for enabling/disabling Windows privileges. This bug did not manifest until I introduced a seemingly innocuous change for EFI encryption (https://sourceforge.net/p/veracrypt/code/ci/c35ab9925fb1d5f28b6130af6f20781ed7207bb5/). It turned out that there was a bug in the SetPrivilege function when disabling a privilege—it was actually removing it instead! This means that the next time we tried to enable it, the operation...
-
Documentation: Update CHM user guide
-
Update Release Notes to mention the fix of EFI regression
-
Windows: Fix bug in disabling of Windows privileges, they were completely removed instead
-
Windows: Fix truncated displayed error message
-
Windows: Update Release Notes for 1.26.15 release to mention MSI related changes
-
Translations: update Russian translation file by Dmitry Yerokhin.
-
Windows: Ensure that installation folder is removed after MSI uninstall by scheduling removal on reboot if needed
-
Windows: Fix MSI not overwriting existing data files (chm, html, xml) with new version
-
Windows: Fix MSI not installing all new documentation file. Remove old files left from old versions. Increment version to 1.26.15.
-
Thank you Doug for providing all these elements, they are very helpful. There was a change in version 1.26.14 involving the functions that are failing, which was implemented to resolve another issue related to encrypting some EFI-based systems. However, it seems this change introduced a problem with setting proper privileges in certain cases during decryption. I will look into it.
-
@anakunda: I was able to reproduce the issue by installing 1.26.7 using the EXE setup and then upgrading to 1.26.14 using the MSI. The issue affects some newly added language files that were not included in the MSI, so after upgrading with the MSI, these language files from the EXE setup remain unchanged. I will need to implement a fix in the MSI to manage these new language files. It looks like a hotfix is coming for the Windows MSI. I will publish version 1.26.15, which includes this fix and another...
-
Documentation: Fix wrong version in Language Packs.html
-
Thank you, @anakunda, for the clarification. I misunderstood the issue. I will try to reproduce the problem on my end because the MSI should have definitely updated the language files.
-
@anakunda: Each version of VeraCrypt comes with updated language files. If you want to use language files from an older version, you can manually edit the file and change the prog-version value in the 3rd line to "1.26.14." However, I strongly recommend using the language files included in the 1.26.14 installers (EXE or MSI). @enigma2illusion: I have updated Language Packs page to point to the ZIP file containing the 1.26.14 language files. Thanks.
-
@petitlou60: This change is only on the virtual device; it is independent of the physical volume. All volumes, both old and new, will benefit from this change.
-
@ukadamr: I have implemented changes in 1.26.14 to overcome this issue. Can you still reproduce it?
-
Wndows: Fix error 1603 returned by MSI silent install when REBOOT=ReallySuppress specified and a reboot is required
-
@petitlou60: It looks like Macrium is encountering an issue with the offset of the VeraCrypt volume, which results in it using a negative value for the free space. I suspect that the following change in version 1.26.14 may have caused this: Fixed failure to format some disks (e.g., VHDX) caused by virtual partition offset not being 4K aligned. In this change, the start offset of VeraCrypt volumes' virtual partition was adjusted from 512 bytes to 1 MiB to align more closely with real disk offsets...
-
@fzxx: The decision to ship driver 1.26.13 with the 1.26.14 release was intentional. I don't build and submit the driver to Microsoft for signing with each build. Submissions are only done when changes impact the driver. In this case, there were no changes between 1.26.13 and 1.26.14 that required rebuilding or resubmitting the driver. Doing so would have added more time, which I didn't have.
-
Thank you for the report. The number 8887 in the error message "MountVolume:8887" indicates the line number in the code of the MountVolume function (in Dlgcode.c) where the error is returned. However, if we check the source code of version 1.26.14, line 8887 of Dlgcode.c does not correspond to an error message: https://sourceforge.net/p/veracrypt/code/ci/master/tree/src/Common/Dlgcode.c#l8887 In fact, the error message should have originated from line 8899. This leads me to believe that the VeraCrypt.exe...
-
@ggiunta: Thank you for your willingness to contribute! I'm glad to hear that the task aligns with your expertise. Regarding your question about discussing details in the forum, it is ok: we aim to keep all activities around VeraCrypt public and transparent, so any input or concerns you have can be openly discussed here. Concerning the crash reporting mechanism, it collects the following information: Program version: The specific version of VeraCrypt that encountered the issue. Operating system version:...
-
As indicated in this documentation page (https://veracrypt.fr/en/Conversion_Guide_VeraCrypt_1.26_and_Later.html), I have developed a tool called VCPassChanger that allows you to convert TrueCrypt volumes in a standalone way, regardless of the current installed VeraCrypt version. It can be downloaded from https://sourceforge.net/projects/veracrypt/files/Contributions/ or from https://launchpad.net/veracrypt/trunk/1.25.9/+download/VCPassChanger_%28TrueCrypt_Convertion%29.zip. In your case, you can...
-
Documentation: Update CHM documentation
-
Thank you @enigma2illusion for the documentation change proposal. I ended up including a variation of your Option 1 as you can see online: From version 1.0f up to and including version 1.25.9, TrueCrypt volumes and non-system partitions created with TrueCrypt versions 6.x and 7.x, starting with version 6.0 released on July 4th 2008, can be converted to VeraCrypt format using any of the following actions: . I hope this aligns with what you proposed.
-
Documentation: Indicate TrueCrypt 6.x and 7.x for the supported TrueCrypt volumes until 1.25.9
-
Translations: Update Russian translation by Dmitry Yerokhin
-
Linux: Add script to sign generated rpms
-
@enigma2illusion: Thank you for your tests. No issue for the false report, I appreciate that you are doing tests even late at night. I have uploaded Windows installers for version 1.26.14 that includes the fix. I started preparing installers of other OSes for this version. I'm intending to publish 1.26.14 as the official release.
-
Increment version to 1.26.14. Set release date to August 25th.
-
Linux/MacOSX: Only load valid XML language files (Language.langid.xml format with langid one of the predefined language identifiers)
-
@enigma2illusion: Yes, the change solves all crashing scenarios. I will provide tomorrow another RC build for Windows that contains the fix.
-
@hiddengod: Thank you for your support and feedback. I completely understand that the lack of a clear roadmap doesn't inspire confidence in donating when a specific feature is the target. While lack of funding for complex tasks like the SSD issue is a factor, another challenge is my inability to guarantee availability due to personal issues I’ve previously explained, which limit my free time. That being said, I am working on finding a way to dedicate more day work time to VeraCrypt in addition to...
-
@aravaara: thank you for your kind words, they mean a lot to me.
-
@ggiunta: Thank you for your offer to help; I really appreciate it. VeraCrypt development is primarily in C/C++, so I'm not sure how much assistance you can provide in that area. However, there is one task on the TODO list where your experience might be valuable. On Linux and macOS, VeraCrypt implements a crash handler to submit crash reports if the user consents. However, this functionality currently does nothing because it has never been implemented on the VeraCrypt website. You can review the...
-
Windows: Fix regression causing crash when a wrong password is used when changing password of volumes
-
Revert "Add Hausa translation (#1404)" (#1407)
-
Add Hausa translation (#1404)
-
Windows: Only load valid XML language files (Language.xx.xml or Language.xx-yy.xml format)
-
Windows: Enhance packaging batch file to bundle only valid XML language files
-
Added some translations to Arabic (#1403)
-
Thank you Enigma2Illusion for your kind words. Indeed, it takes a lot of time to prepare all binaries for all platforms. It's been a long time since I last prepared a full release so setting up the necessary infrastructure is taking some time. I need to think of a way to automate Linux builds while still ensuring the security and integrity of the process as they are the most time-consuming part.
-
@fzxx: I was planning to add it because it seemed simple, but I didn't have enough time to implement it correctly (since it must handle different decimal point values across languages). Additionally, the file container size is a multiple of 512, so if we allow any value, we need to ensure that VeraCrypt's logic is robust enough to ignore extra bytes at the end. So, after all, it's not as simple as it seems.
-
Documentation: refinements, update Russian documentation.
-
Thank you Enigma2Illusion for the feedback. Your suggestions have been incorporated.
-
Thank you Enigma2Illusion for the feedback. I have fixed the README.txt file and I have incorporated your suggestions to the documentation (offline and online).
-
Documentation: Update documentation for TrueCrypt conversion
-
Translations: fix wrong name in an entry id in Ukrainian translation.
-
Added some translations to Ukrainian (#1402)
-
I consider this a Release Candidate for the official version that will succeed 1.26.7 after nearly one year. Therefore, tests and feedback are welcome. Of course, some ongoing issues have not been addressed in this release as they require more work (e.g., ReFS support, Windows driver).
-
@John Navarro: The Linux error code 26 corresponds to EBUSY (Device or resource busy). This indicates that the volume cannot be dismounted because there are still pending I/O operations. This situation typically occurs when the I/O buffer hasn’t been flushed to disk quickly enough before you attempt to dismount the volume. It's important to note that VeraCrypt doesn't control the speed at which I/O buffers are flushed; this is managed by the system based on various factors.
-
Add newly added HTML documentation page to the CHM documentation
-
Thank you, Enigma2Illusion, for the feedback. I have created new documentation (both online and offline) based on your thread: Conversion Guide for VeraCrypt 1.26 and Later. I have made some adaptations to the content. Please let me know your thoughts. Regarding the addition of a "Volume Properties" button to VCPassChanger, this is indeed a great idea. When the user clicks on it, they will be presented with a password dialog. After validation, the properties will be displayed without mounting the...
-
Add missing entry in the Release Notes
-
Update Release Notes. Set release date to August 17th.
-
Documentation: Add conversion guide for deprecated features. Mention hidden volumes in TrueCrypt conversion
-
Translations: Fix encoding issue in Japanese XML file
1 >