Hello Linux folkz, I've already spent three days trying to figure out how to bar SuSEfirewall2 from giving away on the Internet my host and internal network name when SMB is being run. I thoughtfully studded its both configuration files /etc/firewall2.rc.config and /etc/firewall2-custom.rc.config. However, every time I test my box with http://www.grc.com it shows me my host and network name although it's reporting that my port 139 does not appear to exist! I'm pulling my hear through which ports my Linux box is giving away this information? How to block this hole permanently? Could somebody who succeed in this matter send me an example of successfull configuration. Thank you in advance. Alex -- MS Windows users should be covered under the Americans with Disabilities Act! --------------> Try Linux and you'll understand why <--------------
Be sure and block ports 137 and 138 too, both TCP and UDP. Also try
shutting down Samba (rcsmb stop) and try www.grc.com again.
HTH,
Jeffrey
Quoting Alex Daniloff
Hello Linux folkz, I've already spent three days trying to figure out how to bar SuSEfirewall2 from giving away on the Internet my host and internal network name when SMB is being run. I thoughtfully studded its both configuration files /etc/firewall2.rc.config and /etc/firewall2-custom.rc.config. However, every time I test my box with http://www.grc.com it shows me my host and network name although it's reporting that my port 139 does not appear to exist! I'm pulling my hear through which ports my Linux box is giving away this information? How to block this hole permanently? Could somebody who succeed in this matter send me an example of successfull configuration. Thank you in advance. Alex
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
Hello Alex What I do, is to disable samba in Yast, and run "/etc/rc.d/smb start" in the last line of /sbin/SuSEfirewall2. This makes samba visible to LAN, but not internet. Sometimes it helps to think backwards.. Don't change the firewall, start samba after firewall... :-) J. Tamminen Alex Daniloff wrote:
Hello Linux folkz, I've already spent three days trying to figure out how to bar SuSEfirewall2 from giving away on the Internet my host and internal network name when SMB is being run. I thoughtfully studded its both configuration files /etc/firewall2.rc.config and /etc/firewall2-custom.rc.config. However, every time I test my box with http://www.grc.com it shows me my host and network name although it's reporting that my port 139 does not appear to exist! I'm pulling my hear through which ports my Linux box is giving away this information? How to block this hole permanently? Could somebody who succeed in this matter send me an example of successfull configuration. Thank you in advance. Alex
-- MS Windows users should be covered under the Americans with Disabilities Act! --------------> Try Linux and you'll understand why <--------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
Alex Daniloff -
Jaakko Tamminen -
Jeffrey Taylor