-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
did anyone get a response from encrypt.to?
Btw and sorry for this question:
Seems https://encrypt.to to be a reliable service regarding data security?
Transmission of newly created messages are transferred from browser window
to encrypt.to-se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Thursday 1 January 2015 at 5:10:48 PM, in
, Linux Debian wrote:
> those 2 expired subkeys still appear
That should be the case. But the key you attached has only one subkey
(0x1181AAE315915635), and that is all I can see in the web interfa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 01.01.2015 um 18:10 schrieb Linux Debian:
(...)
> I've updated my GnuPG key and send to keyservers. What I updated ?
> I've just deleted 2 expired subkeys and added one with a longer
> (in 2015) expiration. But (...) those 2 expired subkeys stil
Hi guys,
I've updated my GnuPG key and send to keyservers.
What I updated ?
I've just deleted 2 expired subkeys and added one with a longer (in
2015) expiration.
But as I can see in a keyserver -
http://pgpkey.org/pks/lookup?op=vindex&search=0x5935a6bfb301c1aa2218e0e57d58bae0dbeb2b6a&fingerprin
