You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alfred Reibenschuh (JIRA)" <ji...@apache.org> on 2007/07/25 22:46:31 UTC
[jira] Created: (DIRTSEC-8) org.apache.directory.triplesec.otp.Hotp
Class does not conform to RFC4226 Reference Algorithm among other Issues
org.apache.directory.triplesec.otp.Hotp Class does not conform to RFC4226 Reference Algorithm among other Issues
----------------------------------------------------------------------------------------------------------------
Key: DIRTSEC-8
URL: https://issues.apache.org/jira/browse/DIRTSEC-8
Project: Triplesec
Issue Type: Bug
Environment: any
Reporter: Alfred Reibenschuh
@line 62: min/max digits check always false for valid range except 6 and 10.
@line 68: a secret length of 0 is a valid hmac input.
@line 58/76: RFC 4226 has movingFactor method parameter or else uses dynamic offset
patches will follow ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRTSEC-8) org.apache.directory.triplesec.otp.Hotp
Class does not conform to RFC4226 Reference Algorithm among other Issues
Posted by "Alfred Reibenschuh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRTSEC-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alfred Reibenschuh updated DIRTSEC-8:
-------------------------------------
Attachment: hotp.patch
patch to solve issues
> org.apache.directory.triplesec.otp.Hotp Class does not conform to RFC4226 Reference Algorithm among other Issues
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DIRTSEC-8
> URL: https://issues.apache.org/jira/browse/DIRTSEC-8
> Project: Triplesec
> Issue Type: Bug
> Environment: any
> Reporter: Alfred Reibenschuh
> Attachments: hotp.patch
>
>
> @line 62: min/max digits check always false for valid range except 6 and 10.
> @line 68: a secret length of 0 is a valid hmac input.
> @line 58/76: RFC 4226 has movingFactor method parameter or else uses dynamic offset
> patches will follow ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.