Quoting Mark Lodato <lodatom@xxxxxxxxx>: > Any other thoughts, one way or the other? Adding proper SSL/PKI > support would really help git adoption in the corporate world. I am > willing to make any changes necessary to get this into git.git. Somebody mentioned that your patch forces people to type password even when the certificate isn't encrypted. How was this issue addressed? It would be ideal if you can inspect the certificate and decide if you need to ask for decrypting password before using it (and otherwise you don't ask). If you can't do that, probably you can introduce a config var that says "this certificate is encrypted", and bypass your new code if that config var isn't set. That way, people who are used to the old behavior don't have to change anything in their set-up. If people didn't have to type password at all, and after your patch if they are forced to do something else to keep the old set-up working, that isn't nice. -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html