sleepy
Hello everyone
if you are running samba < 2.2.8a then I suggest you upgrade right away, a bufferoverflow has been discovered that allow a remote cracker to execute arbitrary code as the user running samba (which is root) .
more can be found about the patches and newer releases at samba's website
http://www.samba.org
description of the problems as well as code to exploit can be found at
http://www.packetstormsecurity.org
upgrade now, and there is no need for your samba to listen on your external interface. modify your firewall rule or smb.conf
smb.conf : there is a line that starts with listen and some ip, uncomment this line and modify the ip to your internal ip.
firewall rule :
iptables -A INPUT -p tcp -i $EXTERNAL --destination-port 139 -j DROP
(replace $EXTERNAL with the name of your external interface : ppp0 or something)
by the way, there is a very very interesting thing to read at
http://www.openbsd.org
http://www.deadly.org
ssshhhhhhh
if you are running samba < 2.2.8a then I suggest you upgrade right away, a bufferoverflow has been discovered that allow a remote cracker to execute arbitrary code as the user running samba (which is root) .
more can be found about the patches and newer releases at samba's website
http://www.samba.org
description of the problems as well as code to exploit can be found at
http://www.packetstormsecurity.org
upgrade now, and there is no need for your samba to listen on your external interface. modify your firewall rule or smb.conf
smb.conf : there is a line that starts with listen and some ip, uncomment this line and modify the ip to your internal ip.
firewall rule :
iptables -A INPUT -p tcp -i $EXTERNAL --destination-port 139 -j DROP
(replace $EXTERNAL with the name of your external interface : ppp0 or something)
by the way, there is a very very interesting thing to read at
http://www.openbsd.org
http://www.deadly.org
ssshhhhhhh