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.

Sign up for GitHub

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

Jump to bottom

Zeroize sensitive memory in barrier_aes_gcm context #39

Merged
merged 4 commits into from
Feb 5, 2024
Merged

Zeroize sensitive memory in barrier_aes_gcm context #39

merged 4 commits into from
Feb 5, 2024

Commits on Dec 29, 2023

  1. Zeroize sensitive memory in barrier_aes_gcm context 

    As per: Tongsuo-Project#38, this
commit addresses that issue.
    @InfoHunter
    InfoHunter committed Dec 29, 2023
    Configuration menu
    Copy the full SHA
    30f12f2 View commit details
    Browse the repository at this point in the history

  2. Merge remote-tracking branch 'upstream/main' into zeroize

    @InfoHunter
    InfoHunter committed Dec 29, 2023
    Configuration menu
    Copy the full SHA
    fe668c9 View commit details
    Browse the repository at this point in the history

Commits on Jan 2, 2024

  1. fixup! Zeroize sensitive memory in barrier_aes_gcm context

    @InfoHunter
    InfoHunter committed Jan 2, 2024
    Configuration menu
    Copy the full SHA
    513c46e View commit details
    Browse the repository at this point in the history

  2. fixup! fixup! Zeroize sensitive memory in barrier_aes_gcm context

    @InfoHunter
    InfoHunter committed Jan 2, 2024
    Configuration menu
    Copy the full SHA
    f28f5ef View commit details
    Browse the repository at this point in the history