From: "Shawn O. Pearce" <spearce@spearce.org>
To: david@lang.hm
Cc: "Stephen R. van den Berg" <srb@cuci.nl>, git <git@vger.kernel.org>
Subject: Re: [RFC] Adding a challenge-response authentication method to git://
Date: Thu, 14 Aug 2008 14:00:03 -0700 [thread overview]
Message-ID: <20080814210003.GQ3782@spearce.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0808141018220.13400@asgard.lang.hm>
david@lang.hm wrote:
> On Wed, 13 Aug 2008, Shawn O. Pearce wrote:
>
>> Isn't there some authentication frontend that some IMAP servers
>> use to handle the authentication for them? I think last time
>> I setup bincimap it used checkpassword. We might want to do the
>> same if we are going down this road...
>
> are you thinking of SASL?
Maybe I was. But I think I was thinking about DJB's checkpassword
tool. There are several tools that implement the same calling
conventions, some of which link to PAM or an LDAP database, etc.
Plus its fairly easy to create your own if you really needed a
custom solution. You just have to be able to read fd 3. :)
--
Shawn.
prev parent reply other threads:[~2008-08-14 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 16:26 [RFC] Adding a challenge-response authentication method to git:// Stephen R. van den Berg
2008-08-13 16:36 ` Petr Baudis
2008-08-14 7:48 ` David Brown
2008-08-14 8:23 ` Petr Baudis
2008-08-14 11:07 ` Stephen R. van den Berg
2008-08-14 11:39 ` Petr Baudis
2008-08-14 12:14 ` Stephen R. van den Berg
2008-08-13 16:40 ` Shawn O. Pearce
2008-08-13 17:37 ` Stephen R. van den Berg
2008-08-13 18:08 ` Shawn O. Pearce
2008-08-14 0:10 ` Stephen R. van den Berg
2008-08-14 0:57 ` Shawn O. Pearce
2008-08-14 7:13 ` Stephen R. van den Berg
2008-08-14 9:15 ` Andreas Ericsson
2008-08-14 9:51 ` Stephen R. van den Berg
2008-08-14 17:24 ` david
2008-08-14 17:18 ` david
2008-08-14 21:00 ` Shawn O. Pearce [this message]
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=20080814210003.GQ3782@spearce.org \
--to=spearce@spearce.org \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=srb@cuci.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).