A Day in the Life of...

a: $port != 22 is enough to thwart most bots and skiddies. If you think the port number is a guarantee that you are safe or that you are communicating with a blessed ssh you are sadly mistaken. b: Uhh the port number means nothing. Host keys are there for a reason... Someone does not understand the functions of SSH. http://www.snailbook.com/ <- great book c: If you are not investigating fingerprint issues when logging in via SSH and you call yourself a sysadmin, please stop. You are going to be the reason your company ends up in the news because your shit got owned and 2,000,000 user account hashes were leaked blah blah. d: If you are not using key based auth and you have a fly by night keystore policy. Which means you have a keystore - stop. The whole keystore for SSH shit irritates me. I cannot tell you how many times I have heard sysadmins say a that a single private key is a "best practice". It is not a best practice it is a stupid practice and really prevents you from protecting unauthorized logins on other machines for the obvious reasons. Put your public keys on bitbucket.com or source management. Put your private keys on an encrypted disk in an encrypted archive if you must. This is still dumb imho because it is not needed. Leave one account (root) with console only/no ssh access that will allow for keys to be revoked/recreated when users need new keys. e: The original article…

Indeed, magic. How about the Commodore 64, there was a game (Eindeloos, Radarsoft, 1985) within 64kb that has a huge map. Someone recently (after 40 years!) extracted the map (500 screens) and the png alone is 800kb. See the story an zoom in and try finding the little heart in the map! https://adayinthelifeof.nl/2025/03/07/endless.html

The blog post that prompted the author to start this project: I'm fed up with it, so I'm writing a browser (September 2023): https://adayinthelifeof.nl/2023/09/22/browsers.html HN discussion at the time: https://news.ycombinator.com/item?id=37608580

There's so much going on within AWS I'd suggest approaching it the other way and identifying a few examples of things you'd need, and then researching how AWS implements those things - if you need a mainstream relational database, AWS has RDS or Aurora, etc. Need to make sure your RDS database is only accessible from your private backend app? Thats a Security Group. Need somewhere to run that app as a Docker image? ECS or EKS... which may require learning a bit about IAM so you can make sure your own user / deployment user has the right permissions to manage all these resources. Its pretty straightforward to pull a thread - but there are lots of threads you could pull. But this has been shared here before and is still pretty good: https://adayinthelifeof.nl/2020/05/20/aws.html

It's a bad idea, privileged ports are a thing for a reason. https://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html https://adayinthelifeof.nl/2012/03/12/why-putting-ssh-on-another-port-…

Or how memcached does it https://www.adayinthelifeof.nl/2011/02/06/memcache-internals/

Here you go https://adayinthelifeof.nl/2020/05/20/aws.html