From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: Integration with Bugzilla?
Date: Mon, 29 Sep 2014 22:32:23 +0200 [thread overview]
Message-ID: <20140929203223.2104.57735@typhoon.lan> (raw)
In-Reply-To: <5429A5F8.1050504@hupie.com>
On Mon, 29 Sep 2014 at 20:33:28, Ferry Huberts wrote:
> [...]
> my server is guaranteed to have bash, so no need to change it.
> but thanks for the hint anyway :-)
>
I am not (only) talking about portability here. My main concern is the
current spate of bash vulnerabilities. As John pointed out earlier [1],
these can be used to remotely exploit any cgit setup that uses a bash
filter. We currently have at least five CVEs, some of which are very
critical. So if you really want to use bash, you should at least closely
follow the developments and always update your bash binary when there's
a new security patch.
> also, this script is a very minor modification of the script that's in
> the source tree.
>
> --
> Ferry Huberts
>
[1] http://lists.zx2c4.com/pipermail/cgit/2014-September/002236.html
next prev parent reply other threads:[~2014-09-29 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 17:49 joeyisdamanya
2014-09-29 18:07 ` cgit
2014-09-29 18:09 ` mailings
2014-09-29 18:30 ` cgit
2014-09-29 18:33 ` mailings
2014-09-29 20:32 ` cgit [this message]
2014-10-22 1:22 ` joeyisdamanya
2014-10-22 6:29 ` hjemli
2014-10-24 20:25 ` joeyisdamanya
2014-10-26 10:41 ` cgit
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=20140929203223.2104.57735@typhoon.lan \
--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).