[kwlug-disc] How do you keep tabs of your GPG, SSH, and SSL keys?

[Andrew Sullivan Cant]

True. And the GPG and SSH keys have their own pass phrases so they could 
just be stuffed in. Do the SSL keys come with their own encryption?

I looks like there is a cross-platform version of KeePass called 
KeePassX <http://www.keepassx.org/>

Might work, although it appears to lag behind the standard KeePass.

Although I must say that I really like the idea of an encrypted 
container. Having a container which automatically unlocks when I login, 
or unlock my screen, seems like it might be a reasonable balance of 
security.

I have not been able to find a standard secure store format, across 
multiple platforms. Everyone seems to mostly have their own thing 
(gnome-keyring, kwallet, whatever the mac osx one is called) and no 
common format. Which makes me sad.

(And I will happily be corrected, if anyone on the list knows I am wrong :)


Andrew



On 13-03-11 4:46 PM, Chamunks Arkturus wrote:
> Although depending on how robust the keepass encryption is you likely
> don't need to re-encrypt it again because I'm fairly certain that
> keepass does not store your stuff in plaintext.
>
>
> On Mon, Mar 11, 2013 at 4:38 PM, Chamunks Arkturus <chamunks at gmail.com
> <mailto:chamunks at gmail.com>> wrote:
>
>     The pre requisite here is that it needs to be easily cross platform.
>       Alas windows isn't completely dead yet.  As much as we can dream.
>
>     On Mon, Mar 11, 2013 at 3:53 PM, Andrew Sullivan Cant
>     <acant at alumni.uwaterloo.ca <mailto:acant at alumni.uwaterloo.ca>> wrote:
>
>         e-duplication that git would do normally but you get the
>         history. And if there are all smallish files that might be OK.
>
>         AND you central git repository doesn't need to do anything fancy.
>
>         putting all the git repositories into an encrypted store would
>         preserve the history stuff, but then you need the encrypted
>         store stuff working on the server and the client. And I am not
>         quite sure what the right way to handle that would be.
>
>         I guess something like a
>
>
>
>