#Cryptomator ubuntu update#

We actually managed to get a remote screen-shot on the terminal, which was even more unnerving (we figured if Dropbear access was broken, maybe we could log in at the console): The Kill process is part of the unlock script, which means the script is not working…which means the OS can’t find the primary encrypted drive. What is going on? We logged back in, and got the same result. We are trying to unlock our multiple drives. Not only did we see something new, it was also, as far as we can google, unique for a Dropbear login: In fact, we ALWAYS get a prompt for our decryption credentials.

We normally get a prompt for our decryption credentials. We typed in our usual single command and hit the return key: unlock

We waited to login into our Dropbear SSH terminal so we can remotely unlock our encrypted drives. We don’t like that, but that’s the nature of the beast. As usual, the SSH connection was terminated without notice. …at the terminal, as we had done many many times before. So, on our primary server, we issued: sudo reboot That made us feel better ( #FalseSenseOfSecurity). We remotely rebooted the backup server and it worked beautifully.

#Cryptomator ubuntu update#

So, we went to a backup server first, and performed the same update (it was the same OS and it needed the same patches). But this was a security update, so it’s kinda important. So, what could go wrong?Īfter this particular update, which included a kernel change, we were given that lovely notice that says “a reboot is required to make changes take effect”. …commands as our server notified us of routine (so we thought) Ubuntu updates. There we were, minding our own business, running a few standard: sudo apt update & sudo apt upgrade