SSL certificate changes and problems
We recently had to renew our SSL certificates for the
Koumbit.net domain since it's already been a
year since we bought the wildcard on *koumbit.net. Since that
portion of the infrastructure is not completely automated (ie. not provisioned
through Puppet, we forgot to
configure some services, mainly email, which were only configured on Saturday
March 28th. The impact of that is that you may have gotten a warning on that
day and that day only.
Otherwise all connexions to the *.koumbit.net domains should
not generate a warning in most modern browsers. I repeat: if
your browser is generating an error on an SSL-encrypted connexion to our
domains, it is likely to be a man in the middle
attack.
If you need to verify the certificate, you can rely on those fingerprints,
signed with my personnal PGP key.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SHA1 Fingerprint=91:D5:7D:CA:5C:24:84:E6:F9:EC:8F:E3:55:19:A4:A4:E9:50:3E:D1
MD5 Fingerprint=60:D0:AD:42:EC:5C:CD:75:BA:77:9C:63:B8:F2:7C:06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknRCZcACgkQWGBzs0AjcC+7iQCgjaRdDaIMoIgrVURTR0x8FwQ9
CFgAn0q7Buo19n3EGjUPVSqNs5qfW0rh
=pwsu
-----END PGP SIGNATURE-----
MySQL server upgrade
In other news, we have also noticed the recent slowdown of our shared
hosting services and we are working on it. We will install a new database
server during the following weeks which will boast 12GB of ram and two dual
core processors. Since the CPU is back order, there are additional delays in
the delivery of the hardware. We will send another announcement when the server
will be put in production, as this will create a small outage.