On 04/12/2020 10:51, home user wrote:
J. Witvliet responded to my original post, but his response showed up in the list as a new thread. I'm responding here.
(on Dec. 01, 2020 at 02:35am US mountain time, J. Witvliet wrote)
What puzzles me, is that you don’t refer to the firewall. It’s the firewall responsibility to block unexpected incoming, but also outgoing traffic. Often people trust all outgoing traffic on 443 and 80 (and corresponding replies), but you can initially LOG it all, and subsequently change your rules to DROP all you don’t want to see. (Before logging the uncaught)
Please suggest what commands to run to check that what should be blocked is blocked. We already do know that sshd is blocked.
I believe the firewall on your system is already dropping all incoming connection requests.
Provide the output of....
sudo firewall-cmd --get-active-zones
and then using the result from that command
sudo firewall-cmd --info-zone=whatever-was returned.
Example....
[egreshko@f32k ~]$ sudo firewall-cmd --get-active-zones public interfaces: enp1s0
[egreshko@f32k ~]$ sudo firewall-cmd --info-zone=public public (active) target: default icmp-block-inversion: no interfaces: enp1s0 sources: services: dhcpv6-client mdns mountd nfs nfs3 rpc-bind ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
--- The key to getting good answers is to ask good questions.