On Wed Jul 23, 2003 at 01:26:27PM -0700, David Guntner wrote: > > > /etc/cron.daily/msec: line 66: printf: `m': invalid format character > > > /etc/cron.daily/msec: line 66: printf: `@': invalid format character > > > /etc/cron.daily/msec: line 66: printf: `@': invalid format character > > > /etc/cron.daily/msec: line 66: printf: `m': invalid format character > > > > > > Nothing has been changed in that file. This only showed up with the new > > > kernel in place. Please go over the new kernel and release a bugfix for > > > these two problems. Thanks! > > > > Ummm... let's be a little logical here. > > > > Why would you blame the kernel for something in msec? The kernel touches > > /boot and /lib/modules... why would it have anything to do with msec? > > > > Did you look at line 66 of that file? What does it say? > > RPM_VA_CONFIG_DIFF="/var/log/security/rpm-va-config.diff" > > Same as always.
Wierd. > > The previous issue could potentially be attributed to the kernel, but I > > highly doubt it. This one I think attributing to the kernel is pretty > > far-fetched. > > It might very well be. All I know is that the ONLY thing that I changed in > my system last night was to install the new kernel. This morning, I get a > notice about TONS of files (which get created all the time (news, mail, > etc.) being world writable when they never used to be, and the /boot initrd > image being world-writable now sure makes it look like that's the culprit. > And then I get the other error message that I listed above. Yeah, it's a combination of the kernel and your fs. If you were using kernel-secure *or* XFS, you wouldn't see it. I still don't get the msec error tho.. that one is a mystery. > Now, I'm not into blindly blaming a kernel update for all my woes. :-) > However, I *am* pretty good at putting 2 and 2 together. When the ONLY > thing that changes is the kernel, and then weird things start to happen, I > don't think it's unreasonable to suspect that the kernel update *might* be > what's causing that sudden weirdness. Yeah. Like I said, I can see the perms business as being the kernel... that seems to be an established fact. What I don't see is those msec errors... that one really has me scratching my head. > Either way, I appreciate you guys looking into this. Well, we certainly weren't going to ignore it... =) At any rate, 24mdk has been removed from the mirrors... it may take some time, but hopefully it'll get removed before too many others upgrade. And yeah, we're trying to figure this one out. -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp00000.pgp
Description: PGP signature
