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

Deployment keys should not collide with user keys #938

Closed
2 of 6 tasks
evilstiefel opened this issue Feb 14, 2017 · 3 comments
Closed
2 of 6 tasks

Deployment keys should not collide with user keys #938

evilstiefel opened this issue Feb 14, 2017 · 3 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@evilstiefel
Copy link

evilstiefel commented Feb 14, 2017

  • Gitea version (or commit ref): Gitea Version: 1.0.1+1-gab4eb0da
  • Git version: git version 2.11.0
  • Operating system: Linux e94dde8df2eb 3.13.0-108-generic use in instead string join #155-Ubuntu
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When trying to add a SSH key, if it has been used as a deployment key on the site, the user should be warned about that collision and the key be rejected. Otherwise, pushing will simply fail with the following git output:

Gitea: Key permission denied
Cannot push with deployment key: 3
fatal: Could not read from remote repository.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@bkcsoft bkcsoft added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Feb 14, 2017
@lunny lunny added this to the 1.x.x milestone Feb 15, 2017
@stale
Copy link

stale bot commented Feb 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 17, 2019
@lesderid
Copy link

Has this been fixed yet?

@stale stale bot removed the issue/stale label Feb 17, 2019
@zeripath
Copy link
Contributor

Yes. #5939 and #5966 should fix this.

Situations whereby there are already duplicated keys won't be fixed by this PR but new ones won't get produced.

@lunny lunny removed this from the 1.x.x milestone Feb 17, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

5 participants