From: "Alexander Gladysh" <agladysh@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Miklos Vajna" <vmiklos@frugalware.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [Q] Encrypted GIT?
Date: Thu, 13 Mar 2008 16:27:41 +0300 [thread overview]
Message-ID: <c6c947f60803130627r45629099g33a0741f319dc99c@mail.gmail.com> (raw)
In-Reply-To: <20080313125853.GA12927@mit.edu>
> It's normally at this point that that you'd need to bring in a security expert to ask a
> whole lot of questions about your exact use scenario, do a formal
> threat analysis, since there are all sorts of unanswered questions
> about what kind of key management solution you really need for your
> situation.
Uh. This is for kind of hobbyist noncommercial usage, so there are not
that much resources for bringing in security experts. :-)
Also I do not expect this data to be protected from determined (payed)
professional attack -- a determined professional would probably be
able to find some weaker spot elsewhere. However I do want such attack
to cost enough to ward off idle amateurs and bored professionals. :-)
> It's usually not as simple as "just encrypt it".
> How many people need to have access to the to the repository?
Well, 2-5, up to ten, I guess. In immediate future -- two persons only. :-)
> Do you need to revoke access to the repository later?
Probably. But restricting remote access should be enough.
> Who is allowed to give a new person access to the repository?
To keep things simple, me myself only.
> etc., etc., etc.
Thank you,
Alexander.
next prev parent reply other threads:[~2008-03-13 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 8:48 [Q] Encrypted GIT? Alexander Gladysh
2008-03-13 11:47 ` Miklos Vajna
2008-03-13 11:55 ` Johannes Schindelin
2008-03-13 12:16 ` Miklos Vajna
2008-03-13 12:58 ` Theodore Tso
2008-03-13 13:27 ` Alexander Gladysh [this message]
2008-03-13 15:21 ` Johannes Schindelin
2008-03-13 16:00 ` Jeff King
2008-03-13 15:53 ` Jeff King
2008-03-13 16:01 ` Jeff King
2008-03-13 16:12 ` Theodore Tso
2008-03-13 16:19 ` Jeff King
2008-03-13 17:43 ` David Brown
2008-03-13 16:10 ` Thomas Harning
2008-03-13 18:36 ` Luke Lu
2008-03-13 19:15 ` Thomas Harning
2008-03-13 20:06 ` Luke Lu
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=c6c947f60803130627r45629099g33a0741f319dc99c@mail.gmail.com \
--to=agladysh@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vmiklos@frugalware.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).