| Summary: | enable storing SVN passwords encrypted | ||
|---|---|---|---|
| Product: | Community | Reporter: | Nicolas Bros <nicolas.bros> |
| Component: | Subversion | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Nicolas Bros
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. 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. |