Package otp.0.2.2 #29004
Merged
Package otp.0.2.2 #29004
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
jmid
approved these changes
Nov 30, 2025
Member
jmid
left a comment
jmid
left a comment
There was a problem hiding this comment.
LGTM, thanks!
I've made a minor suggestion, but not something that should hold this back.
Co-authored-by: Jan Midtgaard <[email protected]>
Member
|
There's no need for the opam file in your tag to exactly match the version here. Feel free to cherry pick that to your main branch, but this is good to merge as-is to get your package released! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
otp.0.2.2Time-base One Time Password (OTP) based on RFC6238 with an HMAC-SHA1 algorithm and a 6 digits code in OCAML
It relies on the Cryptokit library for cryptography operations, as well as the Base32
library for base32 encoding. The library generate a QR Code with the qrc library. It is
tested against all test vectors provided in RFC 6238 and the test suite provides as well
a dynamic test which requires the use of an client authenticator (like Google Authenticator
or Microsoft Authenticator) as a final test.
🐫 Pull-request generated by opam-publish v2.7.0