[Bug 462624] Re: trouble with stored passwords

Launchpad Bug Tracker 462624 at bugs.launchpad.net
Wed Jun 6 14:57:27 UTC 2012


Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: subversion (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subversion in Ubuntu.
https://bugs.launchpad.net/bugs/462624

Title:
  trouble with stored passwords

Status in “subversion” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: subversion

  I run a new install of Ubuntu Karmic on my home computer.

  I have some svn repositories that i work with, which i have checked
  out to my home computer.

  At home, on my current session everything is working correctly, and
  the login credentials have been stored.

  So i can do a "svn update" without re-entering login credentials.

  However, when I remote connect to my home computer and try to do "svn update" in the ssh shell,
  i get the following message (some details has been censored):

  username at home:/devel/web$ svn update project1
  Authentication realm: <https://servername.com> svn
  Password for 'username': 
  -----------------------------------------------------------------------
  ATTENTION!  Your password for authentication realm:

     <https://servername.com> svn

  can only be stored to disk unencrypted!  You are advised to configure
  your system so that Subversion can store passwords encrypted, if
  possible.  See the documentation for details.

  You can avoid future appearances of this warning by setting the value
  of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
  '/home/username/.subversion/servers'.
  -----------------------------------------------------------------------
  Store password unencrypted (yes/no)? no
  At revision 1473.

  
  I previously ran Jaunty and i did the same things, without this issue.

  I googled the issue and couldnt find a solution, however this does
  seem related to recent changes in the subversion client to work with
  gnome-keyring somehow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/462624/+subscriptions




More information about the foundations-bugs mailing list