intent to enable 2fa requirement for github.com/haskell org
Carter Schonwald
carter.schonwald at gmail.com
Wed Mar 18 23:52:36 UTC 2020
Awesome!
After talking with several folks, feedback has been that best practices are
to make sure the notice is a week before hand.
So what I’ll do is personally reach out to those who aren’t 2fa enabled in
the Haskell gh org (and haven’t commented on this thread )and ask them to
enable 2fa on their GitHub account. Perhaps I should attach a 2fa options
explainer !
I’ll look at folks responses and if everyone active has made the switch
over, I’ll look to do a transition next Monday or Tuesday.
Be well! (Nyc and many other places are pretty strange right now :/ )
-Carter
On Wed, Mar 18, 2020 at 7:42 PM Duncan Coutts <duncan at dcoutts.me.uk> wrote:
> On Wed, 2020-03-18 at 19:05 -0400, Carter Schonwald wrote:
> > No. You don’t. You can use a yubi key and or a totp tool like google
> > Authenticator or 1Password etc. no phones required
>
> It took me a while, but I have successfully managed to turn 2FA back
> into 1FA.
>
> In case it helps anyone else, generate your 2FA response with
>
> $ oathtool --totp -b $the-2fa-secret
>
> Where $the-2fa-secret is the code github gives you after the recovery
> codes (initially shown as a barcode, but they'll give you the actual
> code if you click the link).
>
> > On Wed, Mar 18, 2020 at 6:16 PM Duncan Coutts <duncan at dcoutts.me.uk>
> wrote:
> > > On Wed, 2020-03-18 at 14:46 -0400, Carter Schonwald wrote:
> > > > hey everyone, because so much important stuff for the community, it
> > > > makes sense to add 2fa required for the org, are there any good
> > > > reasons to either wait to do this, or not do it? Feedback welcome!
> > >
> > > I think I might get cut off.
> > >
> > > Is it not still the case that github's 2fa needs a program running on a
> > > mobile phone, or an SMS-capable mobile phone? Is there any support for
> > > normal tools running on a normal Linux machine?
> > >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20200318/aa93eb91/attachment.html>
More information about the ghc-devs
mailing list