self-signed certificates and git

I was working on a system the other day and wanted to pull down some code from my git repository. When pulling down with the git clone https://gitserver.com/username/repository command, I ran into an unexpected error:

error: server certificate verification failed.    CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none while accessing https://gitserver.com/username/repository/info/refs 
fatal: HTTP request failed

Depending on the version of git installed, you may see an error message that is a little more descriptive:

Cloning into 'repository'...
fatal: unable to access 'https://gitserver.com/username/repository.git/': SSL certificate

gitlab

Some time ago now I spun up a server to serve as my own personal code repository using a (now depreciated) gitlab fork known as gitlab-public. This fork added in the ability for there to be public facing projects (like for open-source work) to your gitlab installation. Since this time though gitlab itself has added in this public facing ability upstream, so the use of the fork is no longer needed.

Because we used a fork initially, it made migrating everything back to vanilla gitlab nearly impossible (mostly due to the differing database structures). So in the end we decided

new host, new software

A few months ago the host I was using to host my blog and project2501 got bought out by a big name company in the webhosting / domain registration space. You all know who I am talking about, as this company really has no love lost in the techy world (think stupid commercials with big boobed woman and race cars). They promised that they were going to continue to operate independantly, and currently it seems as if they still are, but who knows how long that will last. Plus I swear I have noticed a degradation of the service lately ... could

'unknown terminal'

This is one of the few posts I wanted to bring over from the old site. It's still relevant and something that I feel that a lot of people run into, especially when using rxvt style terminals

Something I've run into quite a few times is the stupid "terminal unknown" error message when ssh'ing into remote servers. It doesn't happen all the time, but it is very noticeable to me when it does happen, since I use 'clear' a lot, and I can't when this error crops up.

There are essentially two fixes for this, one quicker than the other