Quantcast
Channel: openSUSE Forums
Viewing all articles
Browse latest Browse all 40713

How does SuSEfirewall knows which port belongs to service.

$
0
0
Hi everyone,
I was pocking around susefirewall and being used to RHEL/iptables way of doing things i got little bit confused. From documentation i understood that in /etc/sysconfig/SuSEfirewall2 config file we can define rules, forward/open ports etc. And (in the case of ports) the way we could do it was by specifying port number or service name, like FW_CONFIGURATIONS_EXT="sshd" and firewall would open port 22 for me. I can't find anywhere, though, reference of where SuSefirewall2 gets knowledge about which port belongs to service "sshd"?
Initially i thought that all service names with all corresponding information (ports etc) where defined in /etc/sysconfig/SuSEfirewall2.d/services/{"service-name"} directory. But when i took a look at content of sshd all it sad was: TCP="sshd"- no port number... So please tell me where SuSefirewall2 gets knowledge aout which port belongs to services...

And i have another question not related to "networking", but if i may, instead of creating new thread i ask it here. Superuser privileges - when i installed openSUSE (13.1 very intuitive and easy install procedure btw) i was asked if (first/non-root) user should get administrative rights. I checked that and autologin buttons. After installation was complete, system rebooted and logged me in as was expected without greeting me first with login screen. And i could do "sudo su -" using my user passwd to become superuser. But then another confusion moment.... i expected my user to be in group "wheel", but i was not. So question - where does openSUSE defines its superuser users?

PS please do not direct me to yast, i have found out that i can do almost anything system related with this tool. What i'm really interested in is cli way of doing things.
thnx a bunch

Viewing all articles
Browse latest Browse all 40713

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>