You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of version 1.26.13 imminent, at some point in the distant future or during the revisions being made to the VeraCrypt driver planned for version 1.27, could the multi-threaded code used to decrypt volumes be re-written in Rust? Rust usually offers benefits to concurrent source code and for Windows drivers.
I realise you already use the memory safe C++ functions for operations such as wcscpy/wcscat/strcp and use Coverity but would you consider re-writing some of the code used to allocate and manipulate memory in Rust?
Thanks for all the great work you and all the source code contributors do.
Desired behavior
Dear Mounir,
With the release of version 1.26.13 imminent, at some point in the distant future or during the revisions being made to the VeraCrypt driver planned for version 1.27, could the multi-threaded code used to decrypt volumes be re-written in Rust? Rust usually offers benefits to concurrent source code and for Windows drivers.
I realise you already use the memory safe C++ functions for operations such as wcscpy/wcscat/strcp and use Coverity but would you consider re-writing some of the code used to allocate and manipulate memory in Rust?
Thanks for all the great work you and all the source code contributors do.
Screenshots/Mockup/Designs
N/A
Additional information
https://www.cisa.gov/sites/default/files/2023-12/The-Case-for-Memory-Safe-Roadmaps-508c.pdf
https://www.cisa.gov/sites/default/files/2024-06/joint-guidance-exploring-memory-safety-in-critical-open-source-projects-508c.pdf
https://www.darkreading.com/application-security/shift-memory-safe-languages-gains-momentum
Your Environment
Please tell us more about your environment
VeraCrypt version:
VeraCrypt 1.26.7
Operating system and version:
Windows 11 23H2
System type:
64 bit
The text was updated successfully, but these errors were encountered: