71–80 of 155 posts
Earlier quoted context omitted.
Yeah, but (last time I installed) that wasn't an option at install time.
So then just don't create your main user account at install time. I'm usually creating an 'admin' user at that point anyway. The main thing to watch out for is to add new users appropriately to some system groups like sudo, cdrom, audio and such.
Why create an admin user when root already exists?
Earlier quoted context omitted.
Yeah, but (last time I installed) that wasn't an option at install time.
Ubuntu has that as an install-time feature, but then Ubuntu is definitely not Debian. Then again, Debian isn't really either given the systemd fiasco that is Jessie. How has that whole debacle impacted you? I still have several squeeze(or whatever oldstable / jessie-1 is) boxes that I'm loathe to upgrade, and considering just biting the bullet and switching to either Ubuntu, which has a more mature systemd seutp, or…
Earlier quoted context omitted.
So then just don't create your main user account at install time. I'm usually creating an 'admin' user at that point anyway. The main thing to watch out for is to add new users appropriately to some system groups like sudo, cdrom, audio and such.
> I'm usually creating an 'admin' user at that point anyway. Why create an admin user when root already exists?
You can always delete the user account you created at install time too, after you have set up the root account with a password.
Earlier quoted context omitted.
Store your keys on a hardware token to reduce the chances of this happening (Nitrokey, Yubikey, OpenPGP smart card, etc.)
the way I read about Yubikey is that it is for websites, accounts, etc. Can you use it to log into your actual OS?
There are Yubikey-specific PAM modules you can use as a second factor for logging in locally, and there are probably ways to use standard smartcard authentication for login purposes as well but I don't have experience with that. I mainly use it for remote SSH login purposes.
Earlier quoted context omitted.
That sounds like an annoyance, not encryption to me.
It reminds me of how I set a boot password in the BIOS on my HP laptop. I now have forgot the admin password in order to remove that "feature". I have no idea how I can fix it. The laptop is bricked. I can't install Linux on it because it is set not to boot from USB or CD/ROM
Earlier quoted context omitted.
It reminds me of how I set a boot password in the BIOS on my HP laptop. I now have forgot the admin password in order to remove that "feature". I have no idea how I can fix it. The laptop is bricked. I can't install Linux on it because it is set not to boot from USB or CD/ROM
What's the model number of the laptop?
I use Mac OS X FileVault2, with a firmware password. It's incredibly easy to set up and should be good enough to protect my data from the majority of thieves. Coupled with encrypted Time Machine backups and Arq[0] I feel relatively ok about losing my machine. [0] https://www.arqbackup.com
Earlier quoted context omitted.
The grey coin-sized CMOS battery is alongside the motherboard. I suggest you look at the many guides and videos, just search "removing BIOS password".
That will work for sure? I'd have to really start taking things apart.
I just use Truecrypt 7.1a, and encrypt the entire drive, so it requires a password before booting.