On Monday 26 March 2007 05:19 am, Jon Lewis wrote:

> So does this mean there are infected files in the tarball you kept
> trying to place on that system?

Actually unknown. One of our clients was moving websites and the 
tarballs were backups of the client's home directory.  I doubt anything 
in the directory was anything; after all, it was just a website.  But 
it could have had something bad in it.  The website client (of my 
client) could even have been storing infected files.  Or, since the 
mail on this system is stored in a subdirectory of home, it could have 
been a virus in an email.

However even if it was, deleting the entire tarball wasn't the best 
thing to do.

The home.tar.gz file with the problem was actually inside the 
username.tar.gz file, which it had no problem with, but when the 
automated restore system was trying to restore the site it first 
untarred username.tar.gz, and then tried to untar home.tar.gz. It 
failed a moment later when it couldn't find the tarball.

Jeff
-- 
Jeff Lasman, Nobaloney Internet Services
P.O. Box 52200, Riverside, CA  92517
Our blists address used on lists is for list email only
voice:  +1 951 643-7540, or see: 
"http://www.nobaloney.net/contactus.html"