Skip to content

Conversation

@naveedqadir
Copy link

Add secure memory clearing for sensitive data in AsyncWorker classes. This is a defense-in-depth measure following secure coding best practices.

Changes:

  • Add secure_clear_string() using volatile pointer to prevent optimization
  • Add secure_clear_buffer() for char arrays
  • Update destructors for SaltAsyncWorker, EncryptAsyncWorker, and CompareAsyncWorker to clear sensitive data when workers complete

This ensures passwords and other sensitive inputs don't remain in process memory longer than necessary.

Add secure memory clearing for sensitive data in AsyncWorker classes.
This is a defense-in-depth measure following secure coding best practices.

Changes:
- Add secure_clear_string() using volatile pointer to prevent optimization
- Add secure_clear_buffer() for char arrays
- Update destructors for SaltAsyncWorker, EncryptAsyncWorker, and
  CompareAsyncWorker to clear sensitive data when workers complete

This ensures passwords and other sensitive inputs don't remain in
process memory longer than necessary.
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

Successfully merging this pull request may close these issues.

1 participant