restricting rsync over ssh

[tim.conway at philips.com]

You're dealing with an ssh issue there.  anybody who can't ssh can't rsync 
-e ssh.  Maybe you could take the public keys from everybody you want to 
use it, and put them into the account you want them to ssh into, in 
authorized_keys, with the appropriate command restrictions.

Tim Conway
tim.conway at philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me.... Tim?"




"Brian D. Hamm" <bdhamm at tampabay.rr.com>
Sent by: rsync-admin at lists.samba.org
05/22/2002 12:00 PM

 
        To:     <rsync at lists.samba.org>
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        restricting rsync over ssh
        Classification: 



Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the
rsyncd.conf file is not applicable on the remote since rsync is launched
via the ssh exec call once connected rather than from rsyncd as in a
direct connect.

If so, I am trying to find the best way to restrict rsync -e ssh on the
remote machine.  Prepending the authorized_keys entry with
command='rsync ...' 1024... results in the 'Protocol mismatch - is your
shell clean?' error.

Thanks,

Brian D. Hamm, CISSP, CCNA
Network Design & Implementation
(o) 727-939-3080
(c) 727-424-4384
(f) 240-266-7185
(e) bdhamm at tampabay.rr.com
 



-- 
To unsubscribe or change options: 
http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html