From: melmothx at gmail.com (Marco Pessotto)
Subject: Running CGit with user owning the repository
Date: Fri, 14 Dec 2018 11:24:07 +0100 [thread overview]
Message-ID: <87o99o5rug.fsf@universe.krase.net> (raw)
In-Reply-To: <20181213202414.GA1674@chatter.qube.local>
Konstantin Ryabitsev <konstantin at linuxfoundation.org> writes:
> On Wed, Dec 12, 2018 at 08:11:14PM +0100, Marco Pessotto wrote:
>>this is going to be a dumb question, but are there major concerns about
>>running CGit with the same user owning the repository? Ok, not
>>super-optimal, but is that acceptable?
>
> It's generally not something I'd advise. Of course, CGit does its best
> to remain secure and should not perform any write operations on the git
> repositories it serves. However, this means your defenses are 1 layer
> deep. If a sufficiently bad bug in CGit is found, your repositories are
> now exposed to tampering.
>
> It's best practice not to create systems protected by only one layer of
> defense, because bugs and deployment mistakes will inevitably result in
> security incidents given a long enough period of time. Adding extra
> protection such as different systems users for writing and reading will
> help you hedge against such problems.
Thanks Konstantin for your advise, it seems the best thing to do indeed.
--
Marco
prev parent reply other threads:[~2018-12-14 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 19:11 melmothx
2018-12-13 20:24 ` konstantin
2018-12-14 10:24 ` melmothx [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=87o99o5rug.fsf@universe.krase.net \
--to=cgit@lists.zx2c4.com \
/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).