zzz
eyedeekay, you have anything to report yet from the novg reseed guy?
dolphinandcat
eyedeekay if i made a pr with github actions for the docker image which would be ran by the github mirror of git.idk.i2p would you accept them?
dolphinandcat
to build geti2p/i2p on new release for multiarch
dolphinandcat
and push to hub
zzz
why?
eyedeekay
dolphinandcat make the MR and I'll review it, please take a look at the github-ci file that builds the docker images in order to make sure it integrates with that properly
dolphinandcat
i haven't done it yet
dolphinandcat
because i wasn't sure you'd accept it
dolphinandcat
alright good to know that you're ok with github ci
zzz
you're still not sure. we don't make promises unseen
eyedeekay
Yeah I can't say yes or no until I get a chance to run it
eyedeekay
No response from novg to me yet
eyedeekay
Mail was sent 9 days ago on the 17th
zzz
ok. still holding off on the email to all the reseeds
eyedeekay
tracking an issue with blizzard, ran into a thing
eyedeekay
the signing keys I used for my ShellService plugins are apparently completely gone
eyedeekay
What appears to have happened is that when I was working on my plugin signing tool git.idk.i2p/idk/i2p.plugin.native I mistakenly re-generated and over-wrote my old keys
eyedeekay
Every single key on every single backup I still have retained matches the keys I have been using to sign them locally, which do not match the keys we are currently distributing
eyedeekay
So, in order to resolve it, I'm going to delete these keys that I generated by mistake, generate new keys, and update my plugin cert in i2p.i2p
eyedeekay
Sorry for the inconvenience