rejected updates/pushes can be found on remote

I don't know if this is evil or not. I just find it interesting. If you have and update hook on the remote that returns non-zero, rejecting a push, you can later find the hash (on the remote). I'm glad it get to the remote because I do "git diff --name-only $2 $3" to decide whether or not to accept. But, I wonder if most people are aware that it hangs around until it is garbage collected. This could potentially be an attack vector, or at least a liability. (Imagine some IP troll uploading their code to you and subpoenaing your server.)