Possible Security Violations
=-=-=-=-=-=-=-=-=-=
Feb 16 16:11:34 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed
at tcp.c(2229)
Feb 16 16:11:34 server kernel: KERNEL: assertion
((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at
+af_inet.c(689)
Feb 16 16:11:34 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed
at tcp.c(2229)
Feb 16 16:11:34 server kernel: KERNEL: assertion
((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at
+af_inet.c(689)
Feb 16 16:11:34 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed
at tcp.c(2229)
Feb 16 16:11:34 server kernel: KERNEL: assertion
((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at
+af_inet.c(689)
i've seen a handful of these in the past week or two. which
manpage talks about how to decode this stuff? (is it just a
network snafu or is something serious going on?)
--
I use Debian/GNU Linux version 3.0;
Linux server 2.4.20-k6 #1 Mon Jan 13 23:49:14 EST 2003 i586 unknown
DEBIAN NEWBIE TIP #94 from Joost Kooij <[EMAIL PROTECTED]>
:
How do you RESTORE THE DEFAULT PERMISSIONS back on the / tree?
If you have a clean host with very similar filesystem contents,
try this:
ssh root@okayhost "find / -regex '/\(mnt\|proc\|tmp\)/.*' -prune -or \
-not -type l -not -type s -printf '%04.4m %u %g %p\n' " \
| while read mode user group path
do
chown $user.$group $path
chmod $mode $path
done
Alternatively, create a huge script like this:
find / -regex '/\(mnt\|proc\|tmp\)/.*' -prune -or \
-not -type l -not -type s -printf 'chown %u.%g %p\nchmod %m %p\n' \
> fixperms.sh
And copy that to the broken machine and run "sh fixperms".
It might not fix all files, unless the two hosts are nearly
equal, but enough to let you find the missing ones to fix by
hand. Maybe /home/* will need special care.
Also see http://newbieDoc.sourceForge.net/ ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
