List Info

Thread: Manual incorrectly implies OK in authorization_keys file?




Manual incorrectly implies <cr> OK in authorization_keys file?
user name
2007-04-19 16:18:10
The Subversion manual for 1.4 (compiled from r2782) on page
172
gives an example for embedding an svnserve command within
the
~/.ssh/authorization_keys file:

command="svnserve -t
--tunnel-user=harry",no-port-forwarding,
         no-agent-forwarding,no-X11-forwarding,no-pty 
         TYPE1 KEY1 harryexample.com

I can't speak to other platform configurations, but
OpenSSH_3.5p1
running under Red Hat Linux 9 does NOT appear to respect
the
backslash convention in the authorization_keys file.  My
attempt
at following this example nearly verbatim failed
repeatedly,
ignoring the command option and allowing shell access if
asked.

When I removed the backslashes and carriage returns
everything
worked as advertised.

Perhaps the manual should be amended somehow?

Thanks,
--Bill Burgess

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org


Re: Manual incorrectly implies \<cr> OK in authorization_keys file?
user name
2007-04-23 14:56:35
On 4/19/07, Bill Burgess <burgessgreeneridge.com> wrote:
> The Subversion manual for 1.4 (compiled from r2782) on
page 172
> gives an example for embedding an svnserve command
within the
> ~/.ssh/authorization_keys file:
>
> command="svnserve -t
--tunnel-user=harry",no-port-forwarding,
>          no-agent-forwarding,no-X11-forwarding,no-pty

>          TYPE1 KEY1 harryexample.com
>
> I can't speak to other platform configurations, but
OpenSSH_3.5p1
> running under Red Hat Linux 9 does NOT appear to
respect the
> backslash convention in the authorization_keys file. 
My attempt
> at following this example nearly verbatim failed
repeatedly,
> ignoring the command option and allowing shell access
if asked.
>
> When I removed the backslashes and carriage returns
everything
> worked as advertised.
>
> Perhaps the manual should be amended somehow?

<cr> is a fairly common convention for indicating a
line continuation
in documentation. I see it pretty often in open source
documentation.

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org


Re: Manual incorrectly implies \<cr> OK in authorization_keys file?
user name
2007-04-23 14:59:36
On Apr 19, 2007, at 4:18 PM, Bill Burgess wrote:

> command="svnserve -t
--tunnel-user=harry",no-port-forwarding,
>         no-agent-forwarding,no-X11-forwarding,no-pty 
>         TYPE1 KEY1 harryexample.com
>
> I can't speak to other platform configurations, but
OpenSSH_3.5p1
> running under Red Hat Linux 9 does NOT appear to
respect the
> backslash convention in the authorization_keys file.

Try putting it all on one line.   is often used to indicate
that the  
line continues off the edge of the printed page.

Mark

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org


[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )