public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenSSL: update to 1.1.1f
Date: Wed, 01 Apr 2020 12:38:00 +0000	[thread overview]
Message-ID: <e68ef713-178c-773b-79db-35cfb0041cf6@ipfire.org> (raw)
In-Reply-To: <6C3C7B75-459C-4542-B602-5901684092D4@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

Hello Michael,

not that I am aware of:

> user(a)machine:~/devel/ipfire-2.x> grep -E "^[+-]" log/openssl-1.1.1f | wc -l
> 0

Thanks, and best regards,
Peter Müller


> Lovely.
> 
> Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> 
> Does it not change any root files?
> 
> Best,
> -Michael
> 
>> On 1 Apr 2020, at 13:17, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Fixes #12345 (yes, that's the real bug ID :-) )
>>
>> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
>> Cc: Michael Tremer <michael.tremer(a)ipfire.org>
>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>> ---
>> lfs/openssl | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/lfs/openssl b/lfs/openssl
>> index c46e0d53f..06b999a15 100644
>> --- a/lfs/openssl
>> +++ b/lfs/openssl
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> #                                                                             #
>> # IPFire.org - A linux based firewall                                         #
>> -# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>                     #
>> +# Copyright (C) 2007-2020  IPFire Team  <info(a)ipfire.org>                     #
>> #                                                                             #
>> # This program is free software: you can redistribute it and/or modify        #
>> # it under the terms of the GNU General Public License as published by        #
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER        = 1.1.1e
>> +VER        = 1.1.1f
>>
>> THISAPP    = openssl-$(VER)
>> DL_FILE    = $(THISAPP).tar.gz
>> @@ -87,7 +87,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_MD5 = baeff2a64d2f3d7e0a69b677c9977b57
>> +$(DL_FILE)_MD5 = 3f486f2f4435ef14b81814dbbc7b48bb
>>
>> install : $(TARGET)
>>
>> -- 
>> 2.16.4
> 

  reply	other threads:[~2020-04-01 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 12:17 Peter Müller
2020-04-01 12:33 ` Michael Tremer
2020-04-01 12:38   ` Peter Müller [this message]
2020-04-01 13:12     ` Michael Tremer

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=e68ef713-178c-773b-79db-35cfb0041cf6@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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