From: lalebarde <l.alebarde@free.fr>
To: git@vger.kernel.org
Subject: Re: Transparently encrypt repository contents with GPG
Date: Mon, 18 Jun 2012 13:03:36 -0700 (PDT) [thread overview]
Message-ID: <1340049816370-7561687.post@n2.nabble.com> (raw)
In-Reply-To: <CAL1Gx-Ufs8TNVeeefAXBnX-eCnEk_DC1w6oJVRPcMcStdL_+-Q@mail.gmail.com>
Thanks for your clarifications ! stars 2 & 3 are still not clear for me.
Probably because I am new to git.
Do you think that if a solution is found, in the hypothesis it respects both
git & strong cryptography, it would have success ? My analyse is that small
enterprises that do not have many servers nor premises may need git hosting.
Even big companies with their own networks if they want more security.
TrueCrypt or encrypted file system on the host is not feasible off the
shelves. One have to settle its own dedicated server at the host.
On my side, I am afraid to push my projects in clear into a host. But
possibly I am too much paranoïde. Do you have an idea of the risk ?
--
View this message in context: http://git.661346.n2.nabble.com/Transparently-encrypt-repository-contents-with-GPG-tp2470145p7561687.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-06-18 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 21:19 Transparently encrypt repository contents with GPG Matthias Nothhaft
2009-03-12 21:34 ` Sverre Rabbelier
2009-03-13 10:46 ` Michael J Gruber
2009-03-13 10:51 ` Sverre Rabbelier
2009-03-13 11:15 ` Thomas Rast
2009-03-13 11:17 ` Sverre Rabbelier
2009-03-13 13:56 ` Michael J Gruber
2009-03-13 14:19 ` Sverre Rabbelier
2009-03-13 17:13 ` Jeff King
2009-03-13 20:23 ` Junio C Hamano
2009-03-14 11:16 ` Michael J Gruber
2009-03-14 18:45 ` Junio C Hamano
2009-03-16 16:01 ` Michael J Gruber
2009-03-17 7:40 ` Jeff King
2009-03-17 8:22 ` Jeff King
2012-04-21 17:25 ` bigbear
2012-06-17 7:33 ` lalebarde
[not found] ` <CAL1Gx-Ufs8TNVeeefAXBnX-eCnEk_DC1w6oJVRPcMcStdL_+-Q@mail.gmail.com>
2012-06-18 20:03 ` lalebarde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1340049816370-7561687.post@n2.nabble.com \
--to=l.alebarde@free.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).