Related to team#40317
thank you
Closing this. No longer needed.
@dgoulet is there anything else we can help with here? can you try the cli import?
looking at this guide i think you can just add the key to the list with the x-add-key
command, as a list admin. this also works as a list member:
https://schleuder.org/schleuder/docs/subscribers.html#example-update-your-key-of-a-list-subscription
in other words, you don't need an admin to update your key, before expiry.
from the commandline, you should be able to import sysrqb's key with:
schleuder-cli keys import <list@hostname> </path/to/keyfile>
It just keeps crapping its pants here... I'm getting errors from the keyservers...
I've been doing some list administration for tor-community-council@lists.torproject.org
and noticed that the PGP key listed on the wiki page: https://gitlab.torproject.org/tpo/team/-/wikis/Community-Council#contact
does not match the key retrieved from the schleuder list:
pub rsa4096 2021-01-25 [SC]
057367448EDAD86BB5437642EFE70FF22DA6FDE4
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-request@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-owner@lists.torproject.org>
sub rsa4096 2021-01-25 [E]
I see this was recently generated (about a year ago). We should certainly make sure we update the fingerprint on our public web pages, but I also wanted to check in on the reason for the change and make sure everything is good there.
Documenting the old fingerprint before I make this change to the wiki:
gpg --fingerprint tor-community-council@lists.torproject.org
pub 4096R/0x5FF81BB628254AF3 2017-06-27
Key fingerprint = 78D9 562A AF72 5E6B 3C1F 31AA 5FF8 1BB6 2825 4AF3
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-request@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-owner@lists.torproject.org>
sub 4096R/0x220037F4981C8C4C 2017-06-27
Yeah I guess idk if anything needs to be done. I will update the wiki page with the new fingerprint. It's possible that team#40564 (closed) will supersede this ticket.
I have no clue why we would have a new key tbh ... :S ... did Schleuder auto update it by generating a new one lol ?
i moved this to the schleuder project where it should get the visibility it desserves.
i don't actually know why or if that key changed... can anyone expand on this here? maybe people on the community council? or schleuder admins? @dgoulet ?
i'm not exactly sure what to do with this ticket to be honest.
I've been doing some list administration for tor-community-council@lists.torproject.org
and noticed that the PGP key listed on the wiki page: https://gitlab.torproject.org/tpo/team/-/wikis/Community-Council#contact
does not match the key retrieved from the schleuder list:
pub rsa4096 2021-01-25 [SC]
057367448EDAD86BB5437642EFE70FF22DA6FDE4
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-request@lists.torproject.org>
uid [ unknown] tor-community-council@lists.torproject.org <tor-community-council-owner@lists.torproject.org>
sub rsa4096 2021-01-25 [E]
I see this was recently generated (about a year ago). We should certainly make sure we update the fingerprint on our public web pages, but I also wanted to check in on the reason for the change and make sure everything is good there.
Related to team#40317
thank you
Sorry, I'm slow. I updated my keys, but I didn't request refreshing the keyrings: team#40611 (closed)
Related to team#40317
thank you
Very related: team#40564 (closed)
Hey @sysrqb , so Schleuder is using hkps://hkps.pool.sks-keyservers.net
and I'm unable to make it use something else... Can you maybe upload your key there because at the moment, even with a full re-import manually of your user, I see:
This key expires in 11 days:
0xCE1782624600EE98764C6D9CCB8FC772D1AA1D30 sysrqb@torproject.org 2014-06-26
i think, in this case, you need to talk to the admin of the list you want your key updated on. i'm no schleuder expert, but i believe keys are per list...
oh wait, i guess in team#40317 (closed) ?