Hi there,
> Besides, holding a GPG encrypted keyfile on unencrypted space to open a
> LUKS/dmcrypt encrypted device, opening/decrypting the keyfile in the boot
> process by entering the correct passphrase, to finally open the
> LUKS/dmcrypt secured device seems broken to me.
Can you explain, why
On 24.07.10 08:21, Werner Koch wrote:
The problem though is when I'm trying to get SSH to work with it. It
wont authenticate.
Does "ssh-add -l" sdhow the key?
Yes it shows up here
2010-07-23 20:01:57 gpg-agent[1315] gpg-agent (GnuPG) 2.0.13 started
It would better to try 2.0.16 becuase that
Stanislav Sidorenko writes:
> I've made a quick&dirty fix that enables using SHA256 instead of RIPEMD160.
> hashalgo == GCRY_MD_SHA256? "--hash=sha256 ": "",
>
Okay. I just fixed that and gnupg 1 will now allow all hash
algorithms. Note that this change is only required if
> The problem though is when I'm trying to get SSH to work with it. It
> wont authenticate.
Does "ssh-add -l" sdhow the key?
> 2010-07-23 20:01:57 gpg-agent[1315] gpg-agent (GnuPG) 2.0.13 started
It would better to try 2.0.16 becuase that is the one I can test.
> 2010-07-23 20:03:38 gpg-agen
On 23.07.2010, Grant Olson wrote:
> Just keep in mind that if you're not encrypting the whole disk, your
> sensitive data can leak to /tmp and swap. I'm only bringing this up
> because it seems like you've taken some elaborate steps to protect your
> data.
I second that.
Besides, holding a GP
