Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request (Distant Future): Re-write memory sensitive code and relevant portions of VeraCrypt driver in Rust #1405

Open
hc970 opened this issue Aug 21, 2024 · 0 comments

Comments

@hc970
Copy link

hc970 commented Aug 21, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant