oath-toolkit-help
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OATH-Toolkit-help] Bug#666185: marked as done (Should accept base32 enc


From: Debian Bug Tracking System
Subject: [OATH-Toolkit-help] Bug#666185: marked as done (Should accept base32 encoded keys)
Date: Fri, 01 Jun 2012 07:27:09 +0000

Your message dated Fri, 01 Jun 2012 09:26:46 +0200
with message-id <address@hidden>
and subject line closing
has caused the Debian Bug report #666185,
regarding Should accept base32 encoded keys
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 address@hidden
immediately.)


-- 
666185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666185
Debian Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Should accept base32 encoded keys Date: Thu, 29 Mar 2012 15:20:16 +0100 User-agent: Mutt/1.5.20 (2009-06-14)
Package: oathtool
Version: 1.10.5-1
Severity: wishlist

oathtool currently requires an unencoded key.  It would be nice if it
would also accept base32 encoded keys, so you could pass it e.g. a key
from Google directly.

-- 
Martin Michlmayr
http://www.cyrius.com/



--- End Message ---
--- Begin Message --- Subject: closing Date: Fri, 01 Jun 2012 09:26:46 +0200 User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
This bug should have been closed with the 1.12.0 or 1.12.1 upload,
closing it manually now...

/Simon


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]