To Matthias. My name is John Brumbelow, and I know how to solve your issue. Its requires client-driven-encryption, such that the server never gets the data un-encrypted, ever, and thus can never decrypt it, but yet, on behalf of the client, and other clients, users can still search, partially search, wild-char-search, document-reference-search, and most important, sort data stored on the server, that the server (and its administrators) can never "see" cause it never left the client making/editing it, un-encrypted. Note the key phrase is client-driven-encryption, not, client-encryption. That is, the client drives the encryption process in conjunction with the server(s). This makes it so the data can never be stolen from the server, even if a villan showed up at the server and held the administrators hostage, or at any point beyond the client. There is more... I also know how to further obfuscate the data, as it is being made, to protect the end user, so if the villan showed up at the client, and held them hostage and/or hacked their computer(s), their data would still be protected. This is not just a simple, extra-hash over the data, but something that gives the villan fake/false data, which could be traced/tracked, by the server/authorities. Please email me at John-S-Brumbelow@xxxxxxxxxxx -- View this message in context: http://git.661346.n2.nabble.com/encrypted-repositories-tp3275970p7564308.html Sent from the git mailing list archive at Nabble.com. -- 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