Alexander Jolk wrote:
Paul Bijnens wrote:
Making that one configurable at run time would be easy, but it
would also mean that the suid-root program that invokes tar can be
tricked into executing anything you like, giving root privileges to
anyone.
I don't think amrecover calls tar via runtar
On Fri, May 27, 2005 at 03:47:29PM +0200, Paul Bijnens wrote:
> Alexander Jolk wrote:
> >Eric Dantan Rzewnicki wrote:
> >
> >>Did you compile from source or use the debian package from sid?
> >
> >
> >I compiled from source and installed tar into a different location. Now
> >if only one could spe
Alexander Jolk wrote:
Eric Dantan Rzewnicki wrote:
Did you compile from source or use the debian package from sid?
I compiled from source and installed tar into a different location. Now
if only one could specify which tar to use for amrecover, that would be
most perfect. :-)
Making tha
Eric Dantan Rzewnicki wrote:
Did you compile from source or use the debian package from sid?
I compiled from source and installed tar into a different location. Now
if only one could specify which tar to use for amrecover, that would be
most perfect. :-)
Alex
--
Alexander Jolk /
On Wed, May 25, 2005 at 05:57:43PM +0200, Alexander Jolk wrote:
> Jon LaBadie wrote:
> >Perhaps no postings about the specific problem,
> >but lots where the response was to use 1.13.25,
> >1.13.19, or maybe 1.14.1. Latter one is fairly
> >new, so "my" jury is still out deliberating :)
> BTW I had
Jon LaBadie wrote:
Perhaps no postings about the specific problem,
but lots where the response was to use 1.13.25,
1.13.19, or maybe 1.14.1. Latter one is fairly
new, so "my" jury is still out deliberating :)
BTW I had run into a restoring problem with (Debian sarge's) tar-1.14,
due to `spa
