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

create a mechanism to ensure both sender and receiver of PQcrypt encrypted messages use same version of PQcrypt. #11

Open
Anish-M-code opened this issue Mar 19, 2023 · 0 comments
Labels
enhancement New feature or request feature request good first issue Good for newcomers hacktoberfest help wanted Extra attention is needed

Comments

@Anish-M-code
Copy link
Owner

Since PQcrypt is a rolling release software based on liboqs , maybe as soon as we git clone liboqs locally during installation we must run a sha512 hash over the locally cloned repository and use sha512 hash output as build version, this hash should be added in encrypted messages , the receiver should check this build version with his own and discard message if build versions mismatch. This logic has to be done in code, or perhaps if any better mechanism exists we might think over it.

@Anish-M-code Anish-M-code added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers hacktoberfest feature request labels Mar 19, 2023
@Anish-M-code Anish-M-code changed the title create a mechanism to ensure both sender and receiver of PQcrypt encrypted messages use same version. create a mechanism to ensure both sender and receiver of PQcrypt encrypted messages use same version of PQcrypt. Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request good first issue Good for newcomers hacktoberfest help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant