From: Kate Rhodes <masukomi@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-daemon is insecure? (was: [RFC] Secure central repositories)
Date: Sun, 27 Jan 2008 19:54:41 -0500 [thread overview]
Message-ID: <1201481687.2BC3E4A6@dj11.dngr.org> (raw)
In-Reply-To: 1201481268.12DFA67D@ea27.dngr.org
> UNIX provides the
> tools to do this, because there are cases where it can be useful,
> but really, you have to be nuts to export all of $HOME.
Never ascribe to lunacy what ignorance and stupidity can easily
encompass.
When it comes to security issues you have to try and account for *all*
the idiots.
~kate = masukomi
http://weblog.masukomi.org
next parent reply other threads:[~2008-01-28 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1201481268.12DFA67D@ea27.dngr.org>
2008-01-28 0:54 ` Kate Rhodes [this message]
2008-01-27 10:39 [RFC] Secure central repositories by UNIX socket authentication Shawn O. Pearce
2008-01-27 22:56 ` Junio C Hamano
2008-01-28 0:16 ` git-daemon is insecure? (was: [RFC] Secure central repositories) Shawn O. Pearce
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=1201481687.2BC3E4A6@dj11.dngr.org \
--to=masukomi@gmail.com \
--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).