Re: Insecurity problem?
On Fri, May 11, 2007 at 09:29:08AM +1000, RW wrote: In the past I have always applied relevant patches and recompiled whatever was needed to take care of errata items. Nearly a week ago I decided to use a spare machine to track i386 4.1 stable, did what I was told (FAQ, thanks Nick et al!) : untarred sources, cvs updates, makes all went without hitches and just used a fair few hours. The build box now sends me email every day saying: Checking setuid/setgid files and devices: Setuid/device find errors: find: fts_read: No such file or directory I ran sh -v /etc/security 21 |less and searched for fts_read but the context is just waht you'd expect from the output above. I know that fts_read is a part of find but what is it looking for in vain? I get an itchy feeling that everything did not go as expected during update but the box seems to do whatever I try with no problems. Can you use debug 'echo' statements or somesuch to find out what command causes it? It could indeed be find, although I haven't ever seen this error message from find... Joachim -- TFMotD: rndc (8) - name server control utility
Re: Insecurity problem?
On 2007/05/11 11:36, Joachim Schipper wrote: On Fri, May 11, 2007 at 09:29:08AM +1000, RW wrote: In the past I have always applied relevant patches and recompiled whatever was needed to take care of errata items. Nearly a week ago I decided to use a spare machine to track i386 4.1 stable, did what I was told (FAQ, thanks Nick et al!) : untarred sources, cvs updates, makes all went without hitches and just used a fair few hours. The build box now sends me email every day saying: Checking setuid/setgid files and devices: Setuid/device find errors: find: fts_read: No such file or directory I ran sh -v /etc/security 21 |less and searched for fts_read but the context is just waht you'd expect from the output above. I know that fts_read is a part of find but what is it looking for in vain? I get an itchy feeling that everything did not go as expected during update but the box seems to do whatever I try with no problems. Can you use debug 'echo' statements or somesuch to find out what command causes it? from the output before the error, it must be 'Checking setuid/setgid files and devices': find / \( ! -fstype local \ -o -fstype procfs -o -fstype afs -o -fstype xfs \) -a -prune -o \ -type f -a \( -perm -u+s -o -perm -g+s \) -print0 -o \ ! -type d -a ! -type f -a ! -type l -a ! -type s -a ! -type p [and -print0 and a pipeline, but that's the important bit] Rod, you could try running this under ktrace and see what happens before the 'No such file or directory' error (ENOENT) is displayed, it may give you some clues.
Insecurity problem?
In the past I have always applied relevant patches and recompiled whatever was needed to take care of errata items. Nearly a week ago I decided to use a spare machine to track i386 4.1 stable, did what I was told (FAQ, thanks Nick et al!) : untarred sources, cvs updates, makes all went without hitches and just used a fair few hours. The build box now sends me email every day saying: Checking setuid/setgid files and devices: Setuid/device find errors: find: fts_read: No such file or directory I ran sh -v /etc/security 21 |less and searched for fts_read but the context is just waht you'd expect from the output above. I know that fts_read is a part of find but what is it looking for in vain? I get an itchy feeling that everything did not go as expected during update but the box seems to do whatever I try with no problems. Cluebat? _Rod Depressed? Me? Don't make me laugh! :Spike Milligan:1918-2002:
