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

Regenerate API key #1173

Open
ancarda opened this issue Mar 27, 2021 · 4 comments
Open

Regenerate API key #1173

ancarda opened this issue Mar 27, 2021 · 4 comments
Labels

Comments

@ancarda
Copy link

ancarda commented Mar 27, 2021

Is there any way to regenerate my API key? I've accidentally exposed it... thankfully it's on an unlisted / hard to find page on the Internet, but nevertheless I need to trash this one. There doesn't seem to be a way to request a new API key.

Is this supported by Packagist?

@Seldaek
Copy link
Member

Seldaek commented Mar 27, 2021

I manually reset your API token.

@Seldaek Seldaek closed this as completed Mar 27, 2021
@ancarda
Copy link
Author

ancarda commented Mar 27, 2021

Thank you for resetting my key, @Seldaek!

Can this issue be re-opened as a feature request? It's great that I can ask for the key to be changed, but not so great that it took almost 6 hours for that to happen. A lot of abuse could have happened in that time period.

I noticed within minutes that the key had been printed in the CI logs, but there was nothing I could do about it. Manual revocation really should be possible.

@Seldaek
Copy link
Member

Seldaek commented Mar 27, 2021

Fair enough, I can reopen but given the very few things that the api token allow you to do currently, I don't think this is very high prio. There is little potential for abuse AFAICT.

@Seldaek Seldaek reopened this Mar 27, 2021
@xorinzor
Copy link

Second this. If the API key gets compromised or leaked you'd want to be able to act quickly.

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

No branches or pull requests

3 participants