This video and previous one related to firewalld is pure gold. All the points are made crystal clear with enough explanations and demo. Kudos to the video author. Also, this channel deserve much more subscriptions. I will make sure my linux friends will subscribe to you.
Hi thanks for all your work, I've been enjoying your lessons, they're very informative and descriptive, i just want to ask, if zones are active, is it necessary to set defaults or change zone to ?
hey there, when it comes to necessity of changing those settings for the RHCSA, you should be perfectly alright with knowing when to do it because the test questions are very fair and Red Hat says they don't do trick questions - so it will be clear when you might need to do that as long as you are fully aware that it is something that can be done. Anyways for more detail and practicality, there is a strategic reason for why a sysadmin would ever want to have active zones that are not the default. It allows them to preemptively decide how new network interface traffic is treated, immediately when it appears on the system. You could set a very strict default zone, like drop, for when a connection interface is introduced and then make a case-by-case decision on whether to relocate it to a more trusting zone after the fact. For example, imagine if I had a public kiosk that should only be connected to a specific internal network and then someone very sneaky comes along and plugs in a usb network card and connects my kiosk to their own network so they can covertly attack my machine! That would be a bummer, right? but as one of many ideal layers of defense, I can make sure new automatic network connections aren't handled in an insecure way using firewalld default zones and set up the trusted internal network interface to be explicitly assigned to a non-default zone. That was a loooong response but I hope it helped!
@@beanologi man thank you so much, you surely just did not just help but also explain/clarify the situation , sorry for the late reply, cause I've been watching your videos and I cant thank you enough to show my gratitude, your lessons are the best and i greatly appreciate your purpose sharing your knowledge. you're making it easier !
how this channel doesnt have 5,000 subs from the linux community is insane. this is gold. excellent material
Wow thanks I’m glad you like it! 😊
This video and previous one related to firewalld is pure gold. All the points are made crystal clear with enough explanations and demo. Kudos to the video author. Also, this channel deserve much more subscriptions. I will make sure my linux friends will subscribe to you.
Thank you so much for your hard work. This stuff is very underrated.
Very good series. Thank you!
you explain these concepts articulately. Looking forward for your future contents!
Sitting the exam in a couple days and I cannot thank you enough for your thorough yet clear videos! Subscribed and I hope more do :)
Awesome! You can do it! 💯
@@beanologi Just passed with 286/300, your reviews really saved me on some of the questions, thanks!
@@cyberwave8940Congratulations! 🎉 🎈
Thanks!
Welcome
Nice work, very well explained, way to go. Looking for more such videos! 👍
Thank you!
thanks
Hi thanks for all your work, I've been enjoying your lessons, they're very informative and descriptive, i just want to ask, if zones are active, is it necessary to set defaults or change zone to ?
hey there, when it comes to necessity of changing those settings for the RHCSA, you should be perfectly alright with knowing when to do it because the test questions are very fair and Red Hat says they don't do trick questions - so it will be clear when you might need to do that as long as you are fully aware that it is something that can be done.
Anyways for more detail and practicality, there is a strategic reason for why a sysadmin would ever want to have active zones that are not the default. It allows them to preemptively decide how new network interface traffic is treated, immediately when it appears on the system. You could set a very strict default zone, like drop, for when a connection interface is introduced and then make a case-by-case decision on whether to relocate it to a more trusting zone after the fact.
For example, imagine if I had a public kiosk that should only be connected to a specific internal network and then someone very sneaky comes along and plugs in a usb network card and connects my kiosk to their own network so they can covertly attack my machine! That would be a bummer, right? but as one of many ideal layers of defense, I can make sure new automatic network connections aren't handled in an insecure way using firewalld default zones and set up the trusted internal network interface to be explicitly assigned to a non-default zone.
That was a loooong response but I hope it helped!
@@beanologi man thank you so much, you surely just did not just help but also explain/clarify the situation , sorry for the late reply, cause I've been watching your videos and I cant thank you enough to show my gratitude, your lessons are the best and i greatly appreciate your purpose sharing your knowledge. you're making it easier !
@@niccapistrano555awesome, no problem 👍
This is a bit of an overkill for RHCSA don't you think? Still an phenomenal video!
Ya fair point, I got extra passionate with this one for some reason 😅. Thanks, glad u liked it!