Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336927 - enable storing SVN passwords encrypted
Summary: enable storing SVN passwords encrypted
Status: RESOLVED WORKSFORME
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Subversion (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-11 07:27 EST by Nicolas Bros CLA
Modified: 2011-02-11 09:26 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bros CLA 2011-02-11 07:27:53 EST 
I got the following warning message trying to do a "svn move" on build.eclipse.org:

ATTENTION!  Your password for authentication realm:

   <https://dev.eclipse.org:443> Eclipse Account

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.
Comment 1 Denis Roy CLA 2011-02-11 09:02:57 EST 
Nicolas,

This is the second problem you've encountered while trying to do an SVN move from build, using https.  May I ask why you are not simply using the local filesystem via /svnroot?  I don't see why file:// URLs wouldn't work, and using your own shell account, you won't even need to authenticate to SVN.  The resulting operation would also likely be faster.

Another option: you could use svn+ssh using public key authentication, which is likely even safer than storing password in whatever encrypted format SVN proposes.
Comment 2 Nicolas Bros CLA 2011-02-11 09:26:19 EST 
You are right. I was lazy and copy-pasted the https URLs, but I don't need to commit from build.eclipse.org using https.