I’ve updated my old notes on managing a certificate authority and turned my current usage into a GitLab project. If you are looking at using TLS certificates on a private network, this is a good starting point to learn more about the process and best practices.
Windows Subsystem for Linux is pretty nifty, but Windows has a very rudimentary terminal interface compared to most modern Unix implementations; though I do have high hopes for the new Windows Terminal project. One particularly annoying issue is that there is no way to directly disable sound, this can be a particularly annoying issue when using tab completion or backspace.
The easiest solution to this lack of functionality is to disable the bell in the Linux shell by modifying the
readline(3) configuration in
# do not bell on tab-completion set bell-style none
I just came across this Q&A session with Linus Torvalds regarding the GPL, I was aware of his opinion, but I’ve never heard him talk about it in detail.
I learn well by seeing an example and figuring out what’s going on rather than watching teacher led demonstrations or some other method. I’ve found Go by Example to be the closest thing to my favourite technical manual, the venerable Advanced Bash Guide. For me it’s a great quick reference to understand how apart of the language works when I first encounter it.
I’ve been doing a bit of research for a small project to update project management practices and to refresh my knowledge of 2019’s best practices.
This is a pretty decent high level summary of how to approach password strength.
Update: I’ve since revised these instructions in this post.
This is fairly basic, but you never know what might be useful to somebody!
Due to the fact that WSL doesn’t bootstrap itself with a normal init/systemd process it can be a bit frustrating to work with SSH keys.
ssh-agent command is designed to set up an environment for key management without much hassle. The trivial method of doing this is to insert the following command into your
# start ssh-agent eval `ssh-agent`
This will initialize a socket to manage your keys and you can then use the
ssh-add command as you would on a normal Linux system.
For completeness, stick the following in your
# unset ssh-agent ssh-agent -k
This will remove the socket and unset the environment so that your keys don’t remain loaded after you close your WSL session using
The EFF has just published an article about why nobody should be using ETS. This is particularly timely given the recent finalization of TLS 1.3.
I’ve just written a quick and dirty guide on how to use Certbot on Debian 9 with Route 53. This is useful if you are trying to manage wildcard certificates and don’t want to, or can’t, screw around with managing the current state of the Route 53 plugin on Debian 9.
Without further ado: quay:wiki – Let’s Encrypt Usage Notes