ok about the usernames, in general yes i know this is not ideal .. it just happened this way because the developers needed SSH access to everything essentially so they could mess with things that needed full control ... i think because the ssh password on the server is locked to one single ftp account, so for the developers to have ssh access they needed the root account .. not much i can do about it .. but besides that issue, i need to understand git
On Fri, Jun 28, 2013 at 11:32 AM, Dale R. Worley <wor...@alum.mit.edu>wrote: > > From: HWSWMAN <ed.pat...@gmail.com> > > > > i have a linux server with our website files, and i have me, plus a few > > developers in another country ... myself and the developers share the > same > > SSH access username > > That is generally a bad idea, because then the access of a single > developer cannot be revoked without revoking the access of all the > developers. > > Better is to assign each developer a different username (which can > have a distinct password). Put all the usernames into one group. All > of the things that the developers should have read or write access to > on the server can then be made readable or writable for the entire > group. Also, the various Linux system management tools can see and > record which developer logged in when. > > Dale > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Git for human beings" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/git-users/uZ15XbPK8zk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
