-
To ensure you get the most out of your CIN membership and stay connected with the latest updates, we are asking all members to update their community profiles. Please take a few moments to log in and: • Complete all sections of your profile • Review your current information for accuracy • Enter an alternative email address if desired (CIN requires your valid business email address for your training organization). Keeping your profile up to date helps us better serve you, ensures your account is correctly linked with CompTIA’s CRM, streamlines processes, enhances communication, and guarantees you never miss out on valuable CIN opportunities. Thank you for taking this important step! step!
CIN TTT Series: AutoOps+ V1
- Thread starter Stephen Schneiter
- Start date
Looking forward to this been learning DevOps for delivery but anything that can help me out in an area I've not really covered before will be great.
I'm going through the on-demand for session 1 right now.
Bit of feedback: I'm not a fan that, for logging on Linux, the demo was done with Syslog and /var/log. That's a rather outdated way of working as most modern Linuxen use Journald for their logs. At least the big brand names which students will encounter in the enterprise do so.
I also didn't like that in the JSON vs YAML discussion, it was framed as "JSON is for data, YAML for commands". That's incorrect.
Both JSON, YAML as well as XML are formats for passing data, in the shape of key-value pairs, lists, dictionaries, etc. They all pass data. The fact that Docker uses a Dockerfile's data as build instructions does not make the YAML file "commands", just like Ansible playbooks aren't "commands".
Finally, in the on-demand recording, many times when Tyler's speaking about showing something on his screen, the recording shows the slides; not his screen. For example the Git-section, around the 88 minute mark.
Bit of feedback: I'm not a fan that, for logging on Linux, the demo was done with Syslog and /var/log. That's a rather outdated way of working as most modern Linuxen use Journald for their logs. At least the big brand names which students will encounter in the enterprise do so.
I also didn't like that in the JSON vs YAML discussion, it was framed as "JSON is for data, YAML for commands". That's incorrect.
Both JSON, YAML as well as XML are formats for passing data, in the shape of key-value pairs, lists, dictionaries, etc. They all pass data. The fact that Docker uses a Dockerfile's data as build instructions does not make the YAML file "commands", just like Ansible playbooks aren't "commands".
Finally, in the on-demand recording, many times when Tyler's speaking about showing something on his screen, the recording shows the slides; not his screen. For example the Git-section, around the 88 minute mark.
Last edited:
Thanks for the feedback Tess. I appreciate the heads up about the slides\screen share in the on-demand.
Feedback on session 3, because there's one big mistake.
Right after the 32:00 mark, Tyler claims that "Yubikeys are fingerprint readers, which take a hash of your fingerprint and send it to the system". He shows the Yubikey 5 series.
These are absolutely not what Tyler says; under no circumstance do they work that way. The Yubikey 5 series has a metalic contact which you touch, simply to trigger the electronics inside the device. Fingerprints do not play a role. What does activation do? Either it generates an OTP code, or it lets you sign something with your private key (for key-based login).
Yes, the Yubikey Bio product exists, but that also doesn't do what is claimed. Here, the Yubikey does have a fingerprint reader, but that is only used to activate the cryptographic electronics; your fingerprint is not forwarded anywhere. The device still does the same: OTP, or signing.
Right after the 32:00 mark, Tyler claims that "Yubikeys are fingerprint readers, which take a hash of your fingerprint and send it to the system". He shows the Yubikey 5 series.
These are absolutely not what Tyler says; under no circumstance do they work that way. The Yubikey 5 series has a metalic contact which you touch, simply to trigger the electronics inside the device. Fingerprints do not play a role. What does activation do? Either it generates an OTP code, or it lets you sign something with your private key (for key-based login).
Yes, the Yubikey Bio product exists, but that also doesn't do what is claimed. Here, the Yubikey does have a fingerprint reader, but that is only used to activate the cryptographic electronics; your fingerprint is not forwarded anywhere. The device still does the same: OTP, or signing.