Linux Journal May 2016 by Linux Journal

Author:Linux Journal
Language: eng
Format: mobi, epub
Tags: Privacy, Chrome, Humble Bundle, Features, Bitcoin, Desktop, E-mail, Token-Based, Compromise, Android, Tiny Internet, Configure, Qubes, Glass, Amazon, 4, 9.5, Configuration, Account, Installation, Server, Epichrome, Install, YubiKey, New Math, Security, Purse.IO, PostgreSQL, Secure, Screen Protector, Navigate, KVM, Authentication, Snapchat, Casper, Linux, Gmail, Cloud, Developer
Publisher: Belltown Media
Published: 2016-04-29T07:00:00+00:00

■ Never store private keys on a system that does not have full-disk encryption.

■ Avoid creating passwordless private keys unless you understand the implications of doing so, and have another protection in place to prevent their abuse, such as encrypting the key with a key stored on a separate hardware token.

■ Keep a log of which keys you have in use where, so that if a key is compromised, you can ensure that it is revoked and replaced with a new key.

■ Use a different key on each of your machine. If one of your keys is compromised, once it is used, you know from which key it was which of your machines is in question. If all machines use the same key, you likely will have no idea where the compromise came from. Having multiple keys also is helpful when you are having someone else revoke a key for you. If I find that my laptop’s key may be compromised, but I’m away at a conference, I can make a couple phone calls to get that key revoked in the two or three places where it could cause the most damage. Then, when I get home, I can log in via my desktop (which has its own key) to place a new public key for my laptop in the appropriate places.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.