[jira] [Commented] (SVN-3629) Mechanism to require use of encrypted password store (or none at all)

["Michael Osipov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SVN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210252#comment-15210252 ] 

Michael Osipov commented on SVN-3629:
-------------------------------------

Just wanted to note for those who are reading this issue. I have published https://s.apache.org/svn-enterprise-auth to remedy this ssue.

> Mechanism to require use of encrypted password store (or none at all)
> ---------------------------------------------------------------------
>
>                 Key: SVN-3629
>                 URL: https://issues.apache.org/jira/browse/SVN-3629
>             Project: Subversion
>          Issue Type: Bug
>          Components: libsvn_client
>    Affects Versions: trunk
>            Reporter: C. Michael Pilato
>             Fix For: 1.10-consider
>
>
> {noformat:nopanel=true}
> As Subversion continues to gain traction within enterprise corporations, demands
> around its security consciousness grow.  One such demand has already bubbled up
> to the top of many companies' wishlists:  server-dictated policy that requires
> Subversion clients to either use an encrypted password store when caching
> credentials, or to not cache the credentials at all.
> Subversion makes use of encrypted stores on Windows and Mac by default, and can
> be compiled against GNOME or KDE libs on the Unixes to allow password caching
> via those OSes' keychain mechanisms.  But currently there is no way to require
> (by server-dictated policy) that a user take advantage of these encrypted
> stores.  And therein lies the complaint.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)