Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please add me to this organization #65

Closed
jmw-debian opened this issue Nov 4, 2024 · 5 comments
Closed

please add me to this organization #65

jmw-debian opened this issue Nov 4, 2024 · 5 comments
Labels
auto join automatically created join-requests join join requests

Comments

@jmw-debian
Copy link
Member

jmw-debian commented Nov 4, 2024

Your signed membership application

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

Please add me (Debian user ([email protected]} to this organization
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTdFzjfLGn8URFmteMDXuYJgEtROQUCZyi5ZAAKCRADXuYJgEtR
OU0wAQCy4w8RO/mjqqwKbN0NB8NOUmaEQy64TUp5G3ZKdTD7lQEAh2OQa4wgCTdo
3UYP0pAed7IcO/4N/8z40Q5KbO3J7A0=
=LuKx
-----END PGP SIGNATURE-----
@jmw-debian jmw-debian added auto join automatically created join-requests join join requests labels Nov 4, 2024
Copy link

github-actions bot commented Nov 4, 2024

It seems that the membership application was either not PGP signed at all, or signed with a key that is not currently in the Debian keyring (as offered by https://keyring.debian.org).
The Debian GitHub organization is intended for Debian Developers (DD).

Therefore this issue is closed automatically.
If you feel that this is unwarranted (e.g. because the auto-closing 🤖 has a bug), please leave a comment.

@github-actions github-actions bot closed this as completed Nov 4, 2024
@umlaeute umlaeute reopened this Nov 4, 2024
@umlaeute
Copy link
Contributor

umlaeute commented Nov 4, 2024

@jmw-debian, seems like you did an incomplete paste: the first line should read -----BEGIN PGP SIGNED MESSAGE----- but really did read PGP SIGNED MESSAGE-----, which makes the message not verifiable.

i've fixed the first line, hoping that the bot would re-run, but apparently not.
anyhow, I've manually verified the signature (with the fixed header), which was indeed made by [email protected]

I've re-opened this ticket so @charles-plessy (or somebody else who has the powers) can add you at their earliest convenience.

@charles-plessy
Copy link
Member

Thanks for the help. I just tried to verify the signature too and it gave:

-----END PGP SIGNATURE-----
gpg: Signature made Mon 04 Nov 2024 09:09:08 PM JST
gpg:                using EDDSA key DD1738DF2C69FC511166B5E3035EE609804B5139
gpg: Can't check signature: No public key

Pardon me to be so clumsy with GPG, but can you explain me how to compare this result with CA619D65A72A7BADFC96D280196418AAEB74C8A1, which is what https://db.debian.org reports for Jonathan?

Charles

@umlaeute
Copy link
Contributor

umlaeute commented Nov 5, 2024

@charles-plessy i've added an explanation to #32

@charles-plessy
Copy link
Member

Invitation sent!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto join automatically created join-requests join join requests
Projects
None yet
Development

No branches or pull requests

3 participants