#=======================================================================================================================
    Welcome to SysAdmin Hellweek
#=======================================================================================================================

You are a consultant hired to help customer Idiot Corp who sometimes run into issues with their systems.

Two servers are generally in play:
lab-sysadminserver.xxx.yyy.net (This is the server you will access. It is owned by Idiot Corp and sometimes it experiences issues)
lab-sysadminclient.xxx.yyy.net (This client-server will generate traffic towards the sysadminserver in some of the labs)

- Only the sysadminserver is accessible. Do not connect to the client server.
- Do not change anything on sysadminserver. Do not reboot, modify, restart services etc.
  Regard it as a read-only server as to not mess things up for other participants.

Connect to server:
ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null xxx.yyy.net
Password: iAnalyzeBeforeGoogling

== Important:
- Do not google for the symptoms or errors you see. You would be cheating yourself of an important learning opportunity by googling the fix.
- Do not collaborate with anyone, again, it's important to realize what you yourself know/don't know.
- When you encounter an error, think carefully of what might cause it and work to validate if your assumption of
  cause is accurate. Collect data on it and analyze the data.

== Answer submission
== Submit a short answer to the instructor in private in the following format:

* What is the problem?
-
* How did you reach this conclusion? What commands were used?
-
* If you collected any data, which part of the data showed the problem?
-
* Is there a fix, if so what?
-

#=======================================================================================================================
    Lab #1: Broken SSL/Web-server
#=======================================================================================================================

Customer: Our server can't talk to your www.funbers.com website. You suck and so do does your SSL setup skills.
                   Solve it now or we will buy stuff from your competitor instead!

Assumptions:
- Customer uses cURL on their server to access the www.aaa.com

Mission: Explain to the customer the cause and fix for the problem (if any)

Timeframe: If you've spent more than 30 minutes on this exercise you should most likely as the instructor for a hint

Words of advice: Embrace the pain