On 02/09/2007, at 10:27 AM, Jamis Buck wrote:
> *Feature*: The subversion SCM module no longer uses the --password
> option to authenticate. Instead, it waits until the server prompts for
> the subversion password and send it that way. This is more secure
> ("ps" won't show the password anymore), but I'm not entirely sure what
> the side-effects of this might be, so please report any subversion
> authentication anomalies.
Alright giving this 2.1 preview a burl with some of my more
interesting setups... and though it's great to get rid of the --
password option, it's now prompting for a password locally when
querying for the latest revision.
The culprit is this line in deploy.rb:
_cset(:real_revision) { source.local.query_revision(revision) { |
cmd| with_env("LC_ALL", "C") { `#{cmd}` } } }
but the password handling is in Subversion#handle_data
Is there a way to handle local command streams just like the remote
stream, so we can reuse #handle_data for the query_revision command?
-- tim
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
