Take a stab at these challenges and see how you fare: https://red.ht/ts-1i
Don't forget to give a Kudo to this post and provide your feedback so other's can try this as well. Good luck!
Thanks @Scott for creating this awesome challenge!
Challenge 1
Im so rusty on how to quickly diag a system and how much can go sideways once another starts tinkering with hardening scripts without understanding outcomes after their application.
Yes doing so could cause a RGE (resume generating event)!
Challenge 2
Got bitten too frequently on certain "hardening" standard's guidance and that lesson stuck
Easy Peasy
Nate is the newbie sitting next to Carl #SimplyCyber
I cant complete the second task. any idea?
Hello @gtorreblanca1 !
No worries - I will give you a hint ! I am sure you can figure it out!
look for permissions - which is required to execute a binary !
@gangrif Thanks for pointing that.
I didn't understand this challenge at all as a beginner. I used Google for most of it. I probably wouldn't recommend this for someone who is starting. Maybe for a developer.
Hello @blkwomenread !
Thank you for sharing your feedback and your honest experience with the challenge. It's completely okay to find certain scenarios challenging, especially when you're still in the early stages of your Linux journey.
Troubleshooting scenarios can be challenging, even for experienced Linux users. They require a good understanding of the Linux operating system and its commands. If you're just starting out with Linux, I would recommend starting with some of the beginner-level courses, such as RH124 ,RH134 & RH199. Once you have a good foundation in Linux, you can then try the RHCSA level troubleshooting scenarios.
I also recommend using Google and other resources when you're stuck. There are many helpful resources available online, and they can be a great way to learn new things.
Awesome challange. Looking for the next ones.
Hello!
I am in my initial stages of learning linux and wanted to practice this out. Appreciate any help.
For a. -> I added the VirtualHost block to the httpd.conf, but the /web/html/index.html could not still be accessed. I changed the DocumentRoot by copying the index.html to /var/www/html directory but it would affect production changes. Can someone help with what would be the correct change?
@bongoDB9 - Why do you need to do that ? Why would one change the configuration if all the basic web configuration is right ? First you need to check the logs - what is stopping the webserver to work and then fix that error.
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.