ssh and passwords

[Kevin Bullock]

On 25 Mar 2011, at 6:31 PM, Jason Harris wrote:

> On Mar 26, 2011, at 12:14 AM, Benoit Boissinot wrote:
> 
>> On Fri, Mar 25, 2011 at 11:11 PM, Jason Harris <jason at jasonfharris.com> wrote:
>>> Actually,
>>> 
>>> I have a rough understanding of this and the fact that ssh is asking for these things outside the normal stdin, stdout, stderr. Would there be interest in fixing this by using eg http://www.lag.net/paramiko/ or something similar. Or is there a better way to fix this?
>> 
>> That is not something we want to "fix". Passwords in url for ssh are a
>> *really* bad idea, please use ssh keys if you need interactive mode.
> 
> First: Ok... But then why are passwords in URL's allowed for https?

They are allowed but hidden on output, and since HTTP communication is *not* done by shelling out to an external program, there's no risk of the password showing up in `ps` (unless a user explicitly passes a URL containing a password _to hg_).

By the same reasoning, of course, tools that invoke `hg` should avoid passing HTTP URLs to it that contain passwords.

pacem in terris / mir / shanti / salaam / heiwa
Kevin R. Bullock