Every time Ubuntu releases a LTS version that’s the time I spend time on a version upgrade. Spending few hours on upgrading and some underhood stuff once every six months is not for me, so I decided to stick to LTS.
Today I hit a snag when I was attempting to log into one of our JIRA dev environments where SSO unexpectedly wasn’t working properly and it didn’t let me in.
So here’s my workaround.
Continue reading ““Bypass” JIRA SSO login when SSO isn’t working”
So I’ve been playing around with one of those recent Facebook features. That’s called “Did You Know?” aka Fun Facts.
I kept tapping on “New Question” most of the time because I wasn’t sure what to do with the most. You really need to think more than twice before posting anything on social media these days. Some questions like “A flaw of mine…” are too dangerous to answer unless you’re being sarcastic or posting some smart answer. Also, I my gut feeling tells me that Facebook may use some of the intelligence gathered through fun facts for targeted advertising and marketing. Who wants to be a target, eh?
Do you use Two Factor Authentication with your mobile phone? Do you use your phone as a password recovery option? In case if you are wondering what the hell is two factor authentication, let me simplify it like this. Have you coupled your Gmail/ Facebook/ etc. account with your mobile phone in a way that you receive a ‘code’ that you should enter in the web browser? If so, read on this short note.
So I’ve been reading more on cryptsetup man page and found this interesting excerpt:
If the header of a LUKS volume gets damaged, all data is permanently lost unless you have a header-backup. If a key-slot is damaged, it can only be restored from a header-backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS header is something people manage to do with surprising frequency. This risk is the result of a trade-off between security and safety, as LUKS is designed for fast and secure wiping by just overwriting header and key-slot area.
Yesterday I wrote about How to create an encrypted LUKS disk image.
Today I wanted to experiment more with it. I wanted to try resizing a LUKS volume, and after one failed attempt I found a way. If you still have the disk image of yesterday’s example, just follow me. 🙂
This could be a great alternative if you have used TrueCrypt encrypted volumes.
I’ve been a TrueCrypt lover for a long time, even after it was allegedly killed. But now I’m starting to think that it’s not a good option for long term safekeeping of my memories. At time point in a future release of Linux if dependencies for TrueCrypt stop working that’s death to my archives. Fortunately we have LUKS since 2004! After using LUKS for a couple of years I think it’s very reliable.