This is a reminder that our annual certificate renewal period is coming up soon. Usually, we have our certificates issued some time in December, and certificate issuers allow for a grace period up to some time in January. We’re now in that grace period, so our certificates are going to be renewed and cycled throughout our infrastructure.
A second factor protects your account, but to such extent that if you loose the one device you are normally using, you will have lost access to your account. Hence, we’re going recursive and get you a second second factor (22FA, 2FA^2).
Here’s the process;
- Create a first second factor and call it your Secondary.
- Take a picture or screenshot of the QR code, so that you can print it and store it offline, some place safe.
- Continue with enabling the first, but secondary, second factor and type the validation code so you know everything works.
- Create a new second factor, and confirm the high-security with your Secondary.
- Call the new factor Primary; this will be the one you keep on your phone, and use in your day-to-day.
- In order for this token to be scanned, you’ll have to remove the Secondary from your device.
- Continue with the process of getting your primary second factor on to your device.
- Log out.
- Loose your phone.
Help! Now what?
- Buy a new phone.
- Add back your secondary second factor using the piece of paper stored safely offline.
- Log back in using this backup TOTP-based second factor.
- Go to your settings and remove the primary token; you’ll need to confirm it using your secondary.
- Add a new factor and call it New Primary.
- Remove the secondary from your phone.
- Continue with adding back a primary token and enjoy your new token!
Simple, right? Nothing to it. Too easy.
On Saturday morning (CET) the DNSSEC records expired on one of our DNS servers. This caused a group of customers to have troubles logging in and connecting to Kolab Now services. The record has been renewed and all customers should have access (at 22:49 CET – Please read below).
Secure and confidential communication is an important requirement for a society, and something, I think, we should provide to as many people as possible.
A popular mechanism to achieve this is to use public-key cryptography, which allows a person to encrypt a message to a persons key, so that only the intended recipient can decrypt the message. This means that even if an attacker would get his hands on the encrypted message, without the key, it’s only useless gibberish.
As one of the primary usecases of Kube is communication, it should also support you in doing so in a secure and confidential fashion.