From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: Javantea <jvoss@altsci.com>, Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
aneesh.kumar@gmail.com
Subject: Re: Gitview Shell Injection Vulnerability
Date: Wed, 28 Dec 2016 01:42:55 -0500 [thread overview]
Message-ID: <20161228064255.f4akjdsq24r2hqn7@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGZ79kbOjpi4SBLPVaKXJ+L8VN+0N=ZqgDcHeYydkKsS20yR1Q@mail.gmail.com>
On Tue, Dec 27, 2016 at 10:45:58AM -0800, Stefan Beller wrote:
> > I expect that things that start their life in the contrib/ area
> > to graduate out of contrib/ once they mature, either by becoming
> > projects on their own, or moving to the toplevel directory. On
> > the other hand, I expect I'll be proposing removal of disused
> > and inactive ones from time to time.
>
> Maybe it's time for a spring cleanup and remove some old (dead?)
> projects from contrib?
Yeah, that was my thought on reading the vulnerability report: "that's
still around?". Looks like it hasn't had a substantive commit since
2007. But I dunno, maybe it's just finished, and doesn't need any more
changes. :)
-Peff
next prev parent reply other threads:[~2016-12-28 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 8:29 Gitview Shell Injection Vulnerability Javantea
2016-12-27 18:45 ` Stefan Beller
2016-12-28 6:42 ` Jeff King [this message]
2016-12-28 17:28 ` [PATCH] contrib: remove gitview Stefan Beller
2016-12-29 1:59 ` Jeff King
2017-01-01 0:55 ` Junio C Hamano
2017-01-02 6:46 ` Aneesh Kumar K.V
2016-12-28 19:28 ` Javantea
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161228064255.f4akjdsq24r2hqn7@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jvoss@altsci.com \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).