Chani wrote: >> >Anyways I overall think its a good idea. I'm just frustrated that we >> >had to push back deploying Gitorious.org for Amarok this last weekend >> >due to the push -f issue. >> >> The solution is to have special rights on some accounts. Most >> accounts, including normal developers', would be restricted to the >> normal operations. That is, pushing fast-forward commits to existing >> branches, that's it. >> >> However, we can have those accounts with special rights keyed to >> special SSH keys. And those keys can be distributed. Using those >> accounts would allow to do anything, like deleting or creating >> branches. > >a special ssh key, or a special group...? > >...no, you're right, a special key is better. it's like running as root, > you don't want to do it when you're just working normally. :)
I had thought of special group (admins), but even they can make mistakes.
I prefer the alternative where you choose "*now* I want this special
privilege".
For our internal Git server, we implemented it via a special environment
variable that is passed to the server. But ssh keys serve the same purpose
and don't require a change in the server's sshd_config.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
