git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: John Szakmeister <john@szakmeister.net>
Cc: <git@vger.kernel.org>, Kyle Neath <kneath@gmail.com>,
	Jeff King <peff@peff.net>
Subject: Re: The imporantance of including http credential caching in 1.7.7
Date: Fri, 9 Sep 2011 08:31:20 -0500	[thread overview]
Message-ID: <87boutx2on.fsf@lifelogs.com> (raw)
In-Reply-To: <CAEBDL5VtVZcmQnj2CH7XzZ0YV_X61gO69-dXriGiYsAqk=NLPg@mail.gmail.com> (John Szakmeister's message of "Fri, 9 Sep 2011 06:32:25 -0400")

On Fri, 9 Sep 2011 06:32:25 -0400 John Szakmeister <john@szakmeister.net> wrote: 

JS> [Added back some of the CC's]
JS> Ted: we don't usually cull the CC list on the git mailing list.

Sorry, I followed up via GMane (a NNTP interface to the mailing list).
I'll use `r'eply instead of `f'ollowup.

I actually set

Mail-Copies-To: never
Gmane-Reply-To-List: yes

because I hate getting CC'd on discussions I already follow via GMane.
But that's just my preference :)

JS> 2011/9/9 Ted Zlatanov <tzz@lifelogs.com>:
JS> [snip]
MJG> ... and one for Git on Windows? It seems we're lacking both Win and OS X
MJG> developers here.
>> 
>> Windows doesn't have a standard keychain service, does it?

JS> No, it doesn't, but you can use the wincrypt API which allows you to
JS> at least encrypt the password from the user's login credentials.  In
JS> particular, CryptProtectData() and CryptUnprotectData().  That way you
JS> can at least have the password stored encrypted on disk.

I don't think that's sufficient but could be wrong.

Ted

  parent reply	other threads:[~2011-09-09 13:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  5:33 The imporantance of including http credential caching in 1.7.7 Kyle Neath
2011-09-07  7:46 ` Sverre Rabbelier
2011-09-07  8:11   ` Kyle Neath
2011-09-07 11:21 ` Junio C Hamano
2011-09-07 12:56 ` Michael J Gruber
2011-09-07 20:14   ` Kyle Neath
2011-09-07 21:08     ` Junio C Hamano
2011-09-07 23:01     ` Philip Oakley
2011-09-07 23:38       ` Junio C Hamano
2011-09-08 13:17     ` Michael J Gruber
2011-09-08 15:02       ` John Szakmeister
2011-09-08 19:18         ` Jeff King
2011-09-09  8:05           ` Michael J Gruber
2011-09-09  8:12             ` Miles Bader
2011-09-09 18:27             ` Jeff King
2011-09-08 19:10   ` Jeff King
2011-09-09  8:06     ` Michael J Gruber
2011-09-09 10:15       ` Ted Zlatanov
2011-09-09 10:32         ` John Szakmeister
2011-09-09 10:48           ` Erik Faye-Lund
2011-09-09 10:54             ` John Szakmeister
2011-09-09 13:33               ` Ted Zlatanov
2011-09-09 13:31           ` Ted Zlatanov [this message]
2011-09-09 18:34       ` Jeff King

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=87boutx2on.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=git@vger.kernel.org \
    --cc=john@szakmeister.net \
    --cc=kneath@gmail.com \
    --cc=peff@peff.net \
    /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).