New answers tagged

2

The socket[xxxxx] symlinks are always broken. There isn't a path you can provide to open a socket with a given inode number. I tried it and it seems you can't open the file /proc/pidX/fd/Y which refers to a socket. However you can if it refers to a real file, even if the file has been deleted. It's not exactly a symlink. It's magic (i.e. a special case). ...


0

It appears to be an issue of permission, permission for /etc/ssh/ssh_host_rsa_key /etc/ssh/ssh_host_dsa_key should be such that other users can not access these keys. changed the permission to 700 instead of 755 [root@SC-1 ssh]# ls -l total 156 -rwxr-xr-x. 1 root root 125811 Nov 21 2013 moduli -rwxr-xr-x. 1 root root 2047 Nov 21 2013 ssh_config ...


5

Here's the rules you're looking for: iptables -A INPUT -p tcp -s 202.54.20.22 --sport 5000 -j DROP iptables -A OUTPUT -p tcp -d 202.54.20.22 --dport 5000 -j DROP If the service sends UDP packets, you have to change -p tcp with -p udp.



Top 50 recent answers are included