Skip to content

Conversation

@Heyji2
Copy link

@Heyji2 Heyji2 commented Oct 24, 2025

otp.0.2

Time-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

"md5=0a0f0946ccc2af37eb34132793785db8"
"sha512=49d3d444291ccfa430a846090305beb1b6561e89ae40db8d77aa8eac87ed43af24c58dd7e75ca9bfaa3ec5f65af790d67de07057bfcbc37a5bf8d75f291d247e"
"md5=10e7e9ec1c962298e78e9c3bb2445b59"
"sha512=4acd908ce271ee3ddce899c73383270380e03d3d638d83c61e6de57c0beae4f4e298f6390b970f675a057f6b0519450cf6ed8c0334f0538960475285555baf12"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This updates the checksums of the existing 0.2 release from #28704 which was merged last week.
It is against the opam-repo policy to change these once merged, as it can affect users:
https://github.com/ocaml/opam-repository/tree/master/governance/policies#11-changes-to-a-packages-source-archive-are-prohibited

As your change seems to include a bugfix, I recommend rolling an otp.0.2.1 release containing the fix instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants