If you are in a trusted environment, or you already have an alternative access/authorization mechanism in place, using SSH keys for git is sometimes an annoyance. Turns out you can easily get rid of that, although you should only do that if you are 100% sure what you are doing.
WARNING The following will make your git repository public and anybody will be able to write to it
$ touch .git/git-daemon-export-ok
$ git config daemon.receivepack true
If you receive the following error:
$ git push origin master
Counting objects: 5, done.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 323 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
error: unpack failed: unpacker exited with error code
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to ‘git://server/git/test.git’
Make sure your repository is owned by the user running git-daemon on the server.