Allow to somehow limit access of particular keys to some repositories (BB-4457)

Issue #4156 duplicate
Jacek Bzdak created an issue

Basically I use git and bitbucket not only as a git repository but as as convenient means of deployment, not only deploying my apps on various servers but also deploying examples to presentation machines that I use for lecturing, so some of my production machines have my private key. Which is bad --- because I don;t want to give someone who steals this key address to all my repositories (some of which hold sort of confidential code).

I guess ideal would be to just allow .ssh keys to be limited to particular repositories. For now I circumvent this issue by creating artificial users and sharing these private repos with them (which is OK since as an educational user I have unlimited repo plan) but this approach is kind of problematic since I have to obtain unique email address for each of these users. And it just doesn't feel right to create multiple accounts.

So any means of resolving this problem would be OK.

Comments (4)

  1. Marcus Bertrand staff
    • changed status to open

    It sounds like once we get #3106, we'll be a step further into finding a way to make that happen. I'll leave this open as a second request.

  2. Jacek Bzdak reporter

    Solving #3106 would solve part of my problem --- since some of these repos are read only, but for example when I'll find a bug in code I'm presenting during a lecture --- I correct this bug and I would like to fix it.

    If you extend these deployment keys concept to enable write keys attached to repository all my problems would be solved.

  3. Log in to comment