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

Galaxy does not support signature verification? #1883

Open
samccann opened this issue Sep 13, 2024 · 1 comment
Open

Galaxy does not support signature verification? #1883

samccann opened this issue Sep 13, 2024 · 1 comment
Labels
needs_triage Needs a first human triage before being processed.

Comments

@samccann
Copy link
Contributor

Ansible Galaxy may not support signature verification, but our documentation suggests that it does:
https://docs.ansible.com/ansible/latest/collections_guide/collections_installing.html#installing-collections-with-signature-verification

https://docs.ansible.com/ansible/latest/dev_guide/developing_collections_distributing.html#distributing-collections

Goal of this issue:
1 - Verify that Galaxy doesn't support these features and that they are Automation Hub features only.
2. Remove the misleading documentation.

@ansible-documentation-bot ansible-documentation-bot bot added the needs_triage Needs a first human triage before being processed. label Sep 13, 2024
@samccann
Copy link
Contributor Author

What I've learned so far:

  • The galaxy CLI can validate signatures, regardless of the backend (server - galaxy vs AH).
  • galaxy.ansible.com does not have signatures enabled, but someone can still distribute their own signatures and use the galaxy CLI to verify them.

Still TBD but I'm thinking mentions of AH should be removed at this point. That detail should be in official RH docs, not here in the community docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_triage Needs a first human triage before being processed.
Projects
Status: 🆕 Triage
Development

No branches or pull requests

1 participant