[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RaQ3-All-Security Release 4.0.1-9353 -- Does not update NAMED??
- Subject: Re: [cobalt-users] RaQ3-All-Security Release 4.0.1-9353 -- Does not update NAMED??
- From: "Stephanie Sullivan" <ses@xxxxxxxxxxx>
- Date: Fri Mar 2 04:13:28 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
I found there *does* seem to be a problem! I have 3 RAQ3's and I installed
RaQ3-All-Security Release 4.0.1-9353 for named and
RaQ3-All-Security-4.0.1-9531.pkg for proftpd on all three of them. The gui
indicated they were there, the md5lst files were in the /var/lib/cobalt
directory.
Look good, right? Wrong.
On 2 of the three RAQ's when I ran /usr/sbin/named -v I got the older
version and immediately removed the appropriate .md5lst file and reinstalled
it. When I checked it *then* it was the right version.
Same deal with the proftpd update, but a different 2 of three had the older
version left. Argh.
Like I said above, I'd clearly installed the updates, but the binaries in
/usr/sbin were still the old versions for 2 of 3 cases. I'm worried.
-Stephanie Sullivan
PS - since I installed OS update 4 it seems that /var/log/boot.log does not
get written. It used to... Is this covering the tracks of some kind of a
boot trojan? Anyone else see this on their RAQs? Just want to know if it's
part of a hack or "normal", and how to get this useful diagnostic back...
eh?
-Stephanie
> From: "Jon Rosenberg" <jbr@xxxxxxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Cc: <regis.holstein@xxxxxxxxxx>
> Subject: Re: [cobalt-users] RaQ3-All-Security Release 4.0.1-9353
> -- Does not update NAMED??
> Date: Tue, 27 Feb 2001 14:07:15 -0500
> Reply-To: cobalt-users@xxxxxxxxxxxxxxx
>
> After the update mine reports 8.2.3 on a Raq3
>
> /root]# named -v
> named 8.2.3-REL Thu Feb 8 16:07:37 EST 2001