mainOATH Toolkit - Support: sr #108936, Emergency codes

 
 

sr #108936: Emergency codes

Submitter:  None
Submitted:  Thu 10 Dec 2015 06:30:15 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Wont Do
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 27 Aug 2016 12:40:36 PM UTC, comment #1: 

Thanks for the idea.  I wonder if that idea isn't better implemented as a separated PAM module though?  Is there anything OATH related to the concept of a PAM module doing "emergency scratch codes"?  It appears less complex to have that functionality as a separate module.  And that should be more flexible too.  I am sorry but I don't have time to work on creating that PAM module now though, but it shouldn't be too hard.

I'm leaving this open as a reminder to create such as a PAM module.  Or to revisit my preference for not solving this in pam_oath.

Thanks.

Simon Josefsson <jas>
Group administrator
Thu 10 Dec 2015 06:30:15 PM UTC, original submission:  

Add the ability to use emergency scratch codes in the PAM module, to allow access in case of counter desynchronization or time configuration error, such as google-authenticator does. See https://wiki.archlinux.org/index.php/Google_Authenticator#Generating_a_secret_key_file for UX example. The codes could be stored in the file the same way as the usersfile. The module would delete used codes. The codes could be user-dependent or not. It would be ideal if the PAM module could warn the user if few (1 or 2) emergency codes are still available.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jas (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-08-27 jas StatusNone Wont Do

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code