Hi, El vie., 4 de ene. de 2019 a la(s) 17:17, Jonathan McDowell ( nood...@earth.li) escribió:
> On Fri, Jan 04, 2019 at 09:56:10AM -0300, eamanu15 wrote: > > El lun., 31 de dic. de 2018 a la(s) 05:02, Jonathan McDowell ( > > nood...@earth.li) escribió: > > > On Sun, Dec 30, 2018 at 11:29:33PM -0300, eamanu15 wrote: > > > > I joined to NM and in my personal web I have on *pending *the next > line: > > > > "This is a new entry that requires confirmation before Jan. 2, 2019. > > > > Click here to send the email challenge again." > > > > > > > > I don't receive the email. And when I click on "here" link this give > me a > > > > Server Error (500). > > > > > > > > What would be the problem? > > > > > > Your GPG key has expired, so the system can't encrypt the challenge to > > > you. You need to update your key (and we need to fix the system so it > > > prints a proper error message in that case). > > > > > I am trying to update my keyring using: *gpg --keyserver > > keyring.debian.org <http://keyring.debian.org> --send-keys ...* But I > > don't see the change. On Debian wiki say that this could take some > > time, because the keyring push is monthly. Do you know approx when it > > occur? Or, there are other way to update the key? > > keyring.debian.org is only for keys that are already part of the Debian > keyring, not for new applicants. Your key will be accepted and silently > discarded there. You should send your updated key to the keyserver > network (nm.debian.org is currently using keys.gnupg.net I believe, > which is a pointer to the SKS keyserver network). > Hmmm I've just upload my keyring to keys.gnupg.net. <http://keys.gnupg.net> Currently If I run --recv-key this is ok. But on nm.debian.org still give me the same error :( > > J. > > -- > 101 things you can't have too much of : 17 - Money. > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
