Re: Using tar in forced ssh command?

From: Michael Heiming (michael+USENET_at_www.heiming.de)
Date: 02/22/05 

Date: Tue, 22 Feb 2005 14:59:35 +0100

In comp.security.ssh all mail refused <elvis@notatla.org.uk>:
> In article <2jfre2-qt5.ln1@news.heiming.de>, Michael Heiming wrote:

>>Something like this works as expected:
>> ssh box "tar -cvjf - /path" > file.tar.bz2
>>
>>Now setting a forced command in ~/.ssh/authorized_keys on "box"
>>command="tar -cvjf - /path" ssh-dss ....
>> ssh box > file.tar.bz2
>>file.tar.bz2 isn't a usable tar.bz2 file, it's slightly bigger

> First I'd retry without the compression as it may be easier
> to make sense of what you see.

Doesn't make any different.

> Point a binary editor at the problem file and you'll
> probably find most of it is a tarfile with some extra
> goo on it.

Already done, but it didn't helped me further, that's why I'm
asking here.

> I avoid the use of absolute pathnames in tar as it affects
> the ease of unpacking them to different places.

If you take a close look at my OP, mentioned using Linux, GNU tar
does strip the leading "/" automatically.

Thx for trying to help. 

-- 
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 257: That would be because the software doesn't
work.