git commit --author does not require password? -

My status is as follows: 2 people have access to private repo and work together on code. But a man has written a code on another man's computer and now he does not want to be committed to his name for the name of another name.

I have seen how another author is committed to the repository. I did this, but it is strange that he did not need the author's password, which I was working on. It is not normal, so people can write a code for themselves that I have not written and I am not responsible for this?

GIT does not handle any authority the way it works, you can set your identity to You can do whatever you want by using git config or - author logic. These commitments will remain local on your computer until you decide to push them.

Remote servers often opt for some types of authentication. This is done using the most SSH protocol. In addition, many people add an authorization layer that prevents you from accessing the repository. For example, on GitHub, you can push only for your own repository or that you have got the facility of writing clearly.

This access control only applies to the task of pushing changes so if you have access to a repository, then whatever you want, whatever you want, whatever you want They can push with them too. It is possible that providers add a check that rejects the writers (or commitments) committed by the pushing accused. However, this behavior is not usually desired.

The reason for this is that the GIT is a distributed version control system, unlike above examples, people do not have to use the same centralized server which can then make sure that you are only made by yourself Publish changes (Subversion actually only treats it and "Commits" are only made on the server) Instead, it is possible-and often desired- which run different routes until relying on central registrars (many repositories are normal). You can also work directly with any other developer and make changes or make changes to your personal repository without interacting with any central server at any time. And when you decide to publish commands on a central server, then certainly the central server should not reject your changes because you are involved by another developer.

So, there is no guarantee that someone else is not using your "identity" to make a commit with your name, to ensure that the signature supports signing though You to prove that one has been committed by you, whoever is interested in validating it, then he can see the sign on the commitment and verify that it is in fact Wara was. Some repository servers may also require that all signed papers on the server have been signed, and then confirm the signature on each comma. But this is completely optional and some git does not come by default; Because by default the guitar is just one.