I believe if you don’t have a smartphone handy, you can still use other tools get your auth code. Personally, I use Alfred + the google authenticator workflow, but you can also use Authy (https://www.authy.com/blog/introducing-authy-for-your-personal-computer) and I think it will sync with all your devices. You can also use a personal access token for the command line (works the same way as your SSH key with instructions here: https://github.com/blog/1614-two-factor-authentication).
On September 14, 2016 at 2:41:55 PM, r...@open-mpi.org (r...@open-mpi.org<mailto:r...@open-mpi.org>) wrote: The problem I hit, and the reason I’m pushing back, was that it required me to have a smart phone handy. Not everyone has a smart phone, nor do they always have it sitting next to them. In the case I hit, I was sitting somewhere that (a) had poor cell reception, and (b) didn’t have my cell phone next to me...and so Github refused to let me do something. I’d rather not force that to be the only way we work until some evidence that we have a problem needing to be addressed. > On Sep 14, 2016, at 11:59 AM, Pritchard Jr., Howard <howa...@lanl.gov> wrote: > > Ralph, > > I know with older versions of git you may have problems since you can’t use > https. I think with newer versions it will prompt not just for passed but > also > 2-factor. > > That’s one problem I hit anyway when first enabling 2-factor. > > Howard > > -- > Howard Pritchard > > HPC-DES > Los Alamos National Laboratory > > > > > > On 9/14/16, 12:53 PM, "devel on behalf of Jeff Squyres (jsquyres)" > <devel-boun...@lists.open-mpi.org on behalf of jsquy...@cisco.com> wrote: > >> Sure. There's no rush at all; in fact, this is probably a decent topic >> for our next face-to-face. >> >> >>> On Sep 14, 2016, at 2:46 PM, r...@open-mpi.org wrote: >>> >>> I’d want to _fully_ understand the implications before forcing >>> something on everyone that might prove burdensome, especially when it >>> “solves” a currently non-existent problem >>> >>> >>>> On Sep 14, 2016, at 11:43 AM, Jeff Squyres (jsquyres) >>>> <jsquy...@cisco.com> wrote: >>>> >>>> On Sep 14, 2016, at 2:40 PM, r...@open-mpi.org wrote: >>>>> >>>>>> - Code reviews got better / more organized >>>>>> - Some project management tools now available >>>>>> - We can enforce the use of 2-factor authentication >>>>> >>>>> Please don’t do that... >>>> >>>> Certainly wouldn't do the last one without talking it through with the >>>> community first. >>>> >>>> Is there a reason not to do it? It's not 2-factor on every push -- >>>> it's 2-factor for web logins only, gmail-style (periodically prompt for >>>> 2nd factor on trusted machines, yadda yadda yadda) >>>> >>>> -- >>>> Jeff Squyres >>>> jsquy...@cisco.com >>>> For corporate legal information go to: >>>> http://www.cisco.com/web/about/doing_business/legal/cri/ >>>> >>>> _______________________________________________ >>>> devel mailing list >>>> devel@lists.open-mpi.org >>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel >>> >>> _______________________________________________ >>> devel mailing list >>> devel@lists.open-mpi.org >>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel >> >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> devel@lists.open-mpi.org >> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
