Re: Becareful with up2date over SSH session

On Sat, Jul 31, 2004 at 11:03:22AM -0600, Stephen Smoogen wrote:
> 
> I tried bringing up a RHEL ES system yesterday to the beta channel 
> yesterday. I followed the usual procedure I do with any RHEL box which 
> is to log in via SSH and then do a /usr/sbin/up2date --nox -u
> 
> This normally works and works in most of my beta testing before. However 
> right after downloading all the packages and beginning to update 
> packages, ssh was killed after glibc was updated. This killed the 
> up2date and the DB was in a bad state. It looks like about 20 packages 
> were still on the disk but not in the database so when I was able to get 
> the system going again.. I needed to do a manual rebuild of the RPM 
> database, and then an rpm -Uvh --force /var/spool/up2date/*rpm and then 
> go through the various .rpmsave/new/orig files to see what had been 
> 'lost'. Thankfully not a lot that I can tell.
> 


The only time this has bitten me is when I was working on system
that had a rootkit installed that replaced normal sshd...


-- 
Eduardo Kaftanski
[email protected]
Red Hat Certified Engineer/Instructor/Examiner
Gerente Ingenieria LinuxCenter S.A.
Canada 239 5to Piso, Providencia, Stgo de Chile.
http://www.linuxcenter.cl +56-2-2745000


--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list