From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] squid: add upstream post-3.5.27 security patches
Date: Mon, 22 Jan 2018 17:57:08 +0100 [thread overview]
Message-ID: <87vaftrfvf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180122160816.2246gixwadewjuec@sapphire.tkos.co.il> (Baruch Siach's message of "Mon, 22 Jan 2018 18:08:16 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi Peter,
> On Mon, Jan 22, 2018 at 04:13:39PM +0100, Peter Korsgaard wrote:
>> --- a/package/squid/squid.mk
>> +++ b/package/squid/squid.mk
>> @@ -12,6 +12,9 @@ SQUID_LICENSE = GPL-2.0+
>> SQUID_LICENSE_FILES = COPYING
>> # For 0001-assume-get-certificate-ok.patch
>> SQUID_AUTORECONF = YES
>> +SQUID_PATCH = \
>> + https://github.com/squid-cache/squid/commit/eb2db98a676321b814fc4a51c4fb7928a8bb45d9.patch \
>> + https://github.com/squid-cache/squid/commit/8232b83d3fa47a1399f155cb829db829369fbae9.patch
> Didn't we stop fetching patches from github because they might break the hash
> in the future? See for example commit bbbe00ea35dd2133 (trinity: don't
> download patches from Github).
Hmm, correct - I'll include them in package/squid and resend, thanks!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-01-22 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:13 [Buildroot] [PATCH 1/2] squid: bump version to 3.5.27 Peter Korsgaard
2018-01-22 15:13 ` [Buildroot] [PATCH 2/2] squid: add upstream post-3.5.27 security patches Peter Korsgaard
2018-01-22 16:08 ` Baruch Siach
2018-01-22 16:57 ` Peter Korsgaard [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=87vaftrfvf.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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