You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Shahaf <da...@elego.de> on 2012/03/22 18:02:15 UTC
Re: [Issue 4145] Master passphrase and encrypted credentials cache
Is it now time to review the design doc on the wiki? I've been assuming
it's WIP as I haven't seen a dev@ mail about this feature.
cmpilato@tigris.org wrote on Thu, Mar 22, 2012 at 09:48:15 -0700:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4145
>
>
>
> User cmpilato changed the following:
>
> What |Old value |New value
> ================================================================================
> Status|NEW |STARTED
> --------------------------------------------------------------------------------
>
>
>
>
> ------- Additional comments from cmpilato@tigris.org Thu Mar 22 09:48:15 -0700 2012 -------
> Playing with some implementations over in ^/subversion/branches/master-passphrase
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2938919
>
> To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
Re: AW: [Issue 4145] Master passphrase and encrypted credentials
cache
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 03/23/2012 10:28 AM, Markus Schaber wrote:
> Hi,
>
> Just my 5 ct:
>
> On 03/22/2012 01:02 PM, Daniel Shahaf wrote:
>>> Is it now time to review the design doc on the wiki? I've been
>>> assuming it's WIP as I haven't seen a dev@ mail about this feature.
>
>> Review on the design doc is welcome, yes. I started to explicitly
>> solicit as much, but I found myself in one of those situations where
>> you feel you can't adequately describe implementation specifics because
>> you're still picking through the existing code base. I didn't want to
>> ask folks to review the design only to hear, "Looks good, but how will
>> it work" with me unable to really answer that question. So, if/as you
>> read the wiki page, you may find that some stuff is self-contradictory,
>> unfinished, vague, etc. That's just my ignorance of the authn codebase
>> showing through.
>
> For this to be usable, we'll need some kind of agent which can live
> longer than individual processes. Otherwise, command line work will be
> nearly unusable.
I hear ya. Please read the design doc:
http://wiki.apache.org/subversion/MasterPassphrase
Folks on Windows and MacOSX can have their master passphrases cached in the
OS-provided crypto stores. GNOME keyring and KDE kwallets users on Unix can
get the same. And with the new GPG-Agent support in 1.8, there's that
option for medium-term-but-non-permanent caching, too.
But even folks who don't have those options available a) won't be forced to
use the master passphrase construct at all, and b) if they do use it, will
need only supply a single master passphrase at the command-line. I dunno
about you, but I'd much rather run 'svn update ~/projects/*' and have
Subversion prompt me *once* for a master passphrase than what it does today,
which is prompt me for credentials on each and every working copy in that
directory, nearly all of which come from different servers with different
credentials.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
AW: [Issue 4145] Master passphrase and encrypted credentials cache
Posted by Markus Schaber <m....@3s-software.com>.
Hi,
Just my 5 ct:
On 03/22/2012 01:02 PM, Daniel Shahaf wrote:
>> Is it now time to review the design doc on the wiki? I've been
>> assuming it's WIP as I haven't seen a dev@ mail about this feature.
> Review on the design doc is welcome, yes. I started to explicitly solicit as much, but I found myself in one of those situations where you feel you can't adequately describe implementation specifics because you're still picking through the existing code base. I didn't want to ask folks to review the design only to hear, "Looks good, but how will it work" with me unable to really answer that question. So, if/as you read the wiki page, you may find that some stuff is self-contradictory, unfinished, vague, etc.
> That's just my ignorance of the authn codebase showing through.
For this to be usable, we'll need some kind of agent which can live longer than individual processes. Otherwise, command line work will be nearly unusable.
Best regards
Markus Schaber
--
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
-----Ursprüngliche Nachricht-----
Von: C. Michael Pilato [mailto:cmpilato@collab.net]
Gesendet: Donnerstag, 22. März 2012 18:30
An: Daniel Shahaf
Cc: dev@subversion.apache.org
Betreff: Re: [Issue 4145] Master passphrase and encrypted credentials cache
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: [Issue 4145] Master passphrase and encrypted credentials cache
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 03/22/2012 01:02 PM, Daniel Shahaf wrote:
> Is it now time to review the design doc on the wiki? I've been assuming
> it's WIP as I haven't seen a dev@ mail about this feature.
Review on the design doc is welcome, yes. I started to explicitly solicit
as much, but I found myself in one of those situations where you feel you
can't adequately describe implementation specifics because you're still
picking through the existing code base. I didn't want to ask folks to
review the design only to hear, "Looks good, but how will it work" with me
unable to really answer that question. So, if/as you read the wiki page,
you may find that some stuff is self-contradictory, unfinished, vague, etc.
That's just my ignorance of the authn codebase showing through.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand