[
https://issues.apache.org/jira/browse/SVN-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-3581:
-----------------------------
Description:
When a user logs into a remote OSX system via something like an SSH terminal
connection, the OSX keychain support in SVN does not work. Consequently the
user gets the warning that the password will be saved in plain text and the
entry in the auth area can be modified from a keychain entry to a plain text
entry.
As a workaround, after logging in and before using SVN, the user can use the
following OSX command to manually unlock the keychain:
{noformat}
$ security unlock-keychain
{noformat}
Now, that it is unlocked, SVN can apparently access and use it for its
commands. When you login to OSX graphically, this happens automatically as
part of the login process.
If OSX includes a command line app to do this, then there must also be API's
that SVN could use to do the same. We already do something similar in our
support for GNOME keyring. We even include a command line prompt to unlock the
keyring. We should improve our support for OSX keychain to do something
similar.
http://svnbinaries.open.collab.net/ds/viewMessage.do?dsForumId=65&dsMessageId=354436
was:
{noformat:nopanel=true}
When a user logs into a remote OSX system via something like an SSH terminal
connection, the OSX keychain support in SVN does
not work. Consequently the user gets the warning that the password will be
saved in plain text and the entry in the auth area can
be modified from a keychain entry to a plain text entry.
As a workaround, after logging in and before using SVN, the user can use the
following OSX command to manually unlock the
keychain:
$ security unlock-keychain
Now, that it is unlocked, SVN can apparently access and use it for its
commands. When you login to OSX graphically, this happens
automatically as part of the login process.
If OSX includes a command line app to do this, then there must also be API's
that SVN could use to do the same. We already do
something similar in our support for GNOME keyring. We even include a command
line prompt to unlock the keyring. We should
improve our support for OSX keychain to do something similar.
{noformat}
http://svnbinaries.open.collab.net/ds/viewMessage.do?dsForumId=65&dsMessageId=354436
> OSX keychain support does not work when logged in remotely via Terminal
> -----------------------------------------------------------------------
>
> Key: SVN-3581
> URL: https://issues.apache.org/jira/browse/SVN-3581
> Project: Subversion
> Issue Type: Bug
> Components: unknown
> Affects Versions: 1.6.x
> Reporter: Mark Phippard
> Assignee: Jeremy Whitlock
> Fix For: unscheduled
>
>
> When a user logs into a remote OSX system via something like an SSH terminal
> connection, the OSX keychain support in SVN does not work. Consequently the
> user gets the warning that the password will be saved in plain text and the
> entry in the auth area can be modified from a keychain entry to a plain text
> entry.
> As a workaround, after logging in and before using SVN, the user can use the
> following OSX command to manually unlock the keychain:
> {noformat}
> $ security unlock-keychain
> {noformat}
> Now, that it is unlocked, SVN can apparently access and use it for its
> commands. When you login to OSX graphically, this happens automatically as
> part of the login process.
> If OSX includes a command line app to do this, then there must also be API's
> that SVN could use to do the same. We already do something similar in our
> support for GNOME keyring. We even include a command line prompt to unlock
> the keyring. We should improve our support for OSX keychain to do something
> similar.
> http://svnbinaries.open.collab.net/ds/viewMessage.do?dsForumId=65&dsMessageId=354436
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
