Your message dated Mon, 14 Oct 2019 14:02:07 +0000
with message-id <20191014140207.GB1470@debian>
and subject line
has caused the Debian Bug report #707816,
regarding liboath0: SHA2 support for TOTP
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
707816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liboath0
Version: 2.0.2-2
Severity: wishlist
Hi,
according to RFC6238 section 1.2 [0], "TOTP implementations MAY use HMAC-SHA-256
or HMAC-SHA-512 functions, based on SHA-256 or SHA-512 [SHA2] hash functions".
It would be nice if liboath (and pam_oath) supported this.
Thanks
[0] http://tools.ietf.org/html/rfc6238#section-1.2
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages liboath0 depends on:
ii libc6 2.17-1
liboath0 recommends no packages.
liboath0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
--- End Message ---
