All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: kusmabite@gmail.com, Max Rahm <ac90b671@gmail.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: Feature Request Google Authenticator Support
Date: Thu, 30 Jan 2014 18:22:33 +0100	[thread overview]
Message-ID: <52EA8A59.1030801@gmail.com> (raw)
In-Reply-To: <CABPQNSZmvPH-J=r57_WNjq3WOS7m8dGyrj0Y84etF+8aGAMSiA@mail.gmail.com>

On Thu, 2014-01-30, Erik Faye-Lund wrote:
> On Thu, Jan 30, 2014 at 5:07 AM, Max Rahm <ac90b671@gmail.com> wrote:
>> Github supports google authenticator 2-step authentication. I enabled it
>> and how can't figure out how to connect to my github account through git.
>> I've looked pretty hard in the man pages and on google and can't seem to
>> find anything on how to set up git to work with a repository with 2-step
>> verification. Here's a link to my stackoverflow question with my exact
>> problem if there's something I'm missing.
>>
>> http://stackoverflow.com/questions/21447137/git-github-not-working-with-google-authenticator-osx
>>
>> As far as I can tell the feature is not supported. I'd like to be able to
>> use the 2-step authentication but obviously I'd like to be able to push my
>> code :D
>
> This sounds like a question for the GitHub support rather than the Git
> community.

Especially that Git prides itself that it does not do authenthication,
but passes it to appropriate programs, SSH or web server (HTTP).

Own git:// protocol is unathenthicated.
-- 
Jakub Narębski

  reply	other threads:[~2014-01-30 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30  4:07 Feature Request Google Authenticator Support Max Rahm
2014-01-30  4:18 ` Andrew Ardill
2014-01-30 14:28 ` Erik Faye-Lund
2014-01-30 17:22   ` Jakub Narębski [this message]
2014-01-30 17:38   ` Scott Chacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52EA8A59.1030801@gmail.com \
    --to=jnareb@gmail.com \
    --cc=ac90b671@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kusmabite@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.