Updating public key problem

[MFPA]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi


On Thursday 1 January 2015 at 5:10:48 PM, in
<mid:54A57F98.3070503 at zoho.com>, 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 interface
of three different keyservers. I also do not pick up any additional
subkeys in GnuPG if I refresh your key from a keyserver.



> and that's why, in
> my opinion, why the sending an encrypted message
> doesn't work by the free service like -
> https://encrypt.to/linuxdebian@zoho.com Before the
> expirationd date of those 2 keys, the encrypt.to
> service worked.

If that is the reason, there must be an awful lot of keys that would
not work with that service. However, in the absence of error messages
it is hard to diagnose the reason. Maybe the people who run encrypt.to
might be willing to help you.

My current and previous keys don't work there, and nor do a couple of
test keys I have knocking around. Two of the four cause the page to
freeze and block input to the message compose window, with no error
message at all - just like yours does. One generates a message saying
there is no key id associated with that email address, or there is no
email address associated with that key id - yet I can retrieved it
from a keyserver by searching on the email address. The fourth one
encrypts the message in the box, then (because the UID intentionally
intentionally contains an unrouteable address) produces the rather
uninformative error message "Oops! Something went wrong. Please try
again."



> Thanks for any tip how to correctly update or what to
> do, so my public key would be possible to be used by
> encrypt.to for those who wanna send me a private
> message.

Does encrypt.to cope with 4096-bit keys and SHA256 binding signatures?
What size was your old encryption subkey?



- --
Best regards

MFPA                    mailto:2014-667rhzu3dc-lists-groups at riseup.net

ETHERNET(n): device used to catch the Ether bunny
-----BEGIN PGP SIGNATURE-----

iQF8BAEBCgBmBQJUpqtsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwc+sIAKwD5ww3Dx1vOMYxD5xW56Gz
xOk/qWbTtCSRNlYdKoqlDCAqRzJBObN8xDmFjSkx/xOVXHSN8+5Y4SBzLtZ79uGW
LpM/62zZwQa3BqYgBz3TyAty2Atsfai94opDkIrUQI2nV0Z4fOHeEWDXVj2qWZY4
j8hBn0iZMnzwslQkEY3S6ZXdeDUCVP1TkYowSo5wlvlTc3KaQCjHY24mthVM3mpT
2MaBYFpp6Lun8xkfm6Zd/Pye48PiwR5HxuBnnQD3L4s6PBDHIWVBD/QozkDdLSvM
PgIIKuEfCRa2sh4CFiPqI+epOnIkJq3noYp5NO8kWyw7hDIH8QwYOHNto+KowmiI
vgQBFgoAZgUCVKarbF8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45KIQAQDF7OS1wnJu7VhFwhbZ8Uj9byTr
INYY7KtuQZQFN8pT5gEAsnskB0jHrp3FqCAUgsPzbAgt+Z9KyRelHd5IPbEF0g4=
=G4T1
-----END PGP SIGNATURE-----