If you’re an IT professional that has to deal with old systems that have self-signed certificates you most probably had to add exceptions to your browser many times. Maybe even import those self-signed certificates locally. Unfortunately when you’re working on a customer’s jump host this is not an option. And starting with more recent version of Chrome this is not possible anymore, you don’t have the option to Add it as an exception....

Have you ever wanted to just start a Webserver in a second, for a quick and dirty task but didn’t want to install a full LAMP/LEMP stack? This is possible with the help of a python module and here it is in action: costin@ubuntu:~$ mkdir testare costin@ubuntu:~$ cd testare/ costin@ubuntu:~/testare$ echo MERGE! > index.html costin@ubuntu:~/testare$ pushd $PWD; python3 -m http.server; popd ~/testare ~/testare Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ....

On F5 BigIP LTM you can create a SSL profile even if you don’t know the private key passphrase This workaround can be applied only if you’ve used the private key on the same F5 BigIP node already. In my case, I had to reuse the same cert+key from a server-ssl profile on a client-ssl profile. And because business was in a hurry and they didn’t have the private key anymore, I had to find alternative ways of making it work....

So recently I’ve encountered the error in the subject. This came after 2 major changes (OS upgrade and PHP upgrade). So definitely it had to do with one of them. My money were on the first one. I’ve looked around on the internet and the only thing I could see was this old article that had no solution: https://www.digitalocean.com/community/questions/do-agent-exited-with-a-return-code-100 So I knew I had to take the matters in my own hands....

ctrl+alt+end