[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bug with svn+ssh (plus workaround)

From: Alan Barrett <apb_at_cequrux.com>
Date: 2006-03-21 17:48:07 CET

On Tue, 21 Mar 2006, Joseph Galbraith wrote:
> Alan Barrett wrote:
> > This doesn't work:
> >
> > svn log svn+ssh://host/repo/trunk 2>&1 | less
> >
> > The symptom is that the output is truncated after the first few
> > kilobytes.
> > [...]
> > As a fix, I suggest that svn should connect ssh's stdout to a pipe
> > that is managed by svn.
>
> I assume you meant stderr here, since it already does so
> with stdout (according to your message.)

Yes, I meant "stderr".

> The reason not to do this is that ssh uses stderr to prompt
> for authentication credentials. By leaving stderr connected
> to terminal (in most cases) the user can actually type
> his password/passphrase/whatever to authenticate
> to the server. If we redirect stderr, then this will no
> longer work.

I didn't mean "connect ssh's stderr to a pipe that swallows the output",
I meant "connect ssh to a pipe that copies the output to the user".

Anyway, ssh tries to use /dev/tty in preference to stderr for
authentication prompts. If /dev/tty doesn't work, then it tries to
prompt on stderr and read from stdin, but it's unlikely that that will
work when ssh's stdin is a pipe to svn.

--apb (Alan Barrett)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 21 17:54:20 2006

This is an archived mail posted to the Subversion Dev mailing list.