public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Net-SSLeay: Update to version 1.88
Date: Mon, 21 Oct 2019 13:14:21 +0200	[thread overview]
Message-ID: <1be42b28fe36567546d95fb26c5dc4cecab4971e.camel@ipfire.org> (raw)
In-Reply-To: <1C064FFB-FE2A-4130-9CDE-F738A0D440FC@ipfire.org>

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

Hi Michael,

On Mo, 2019-10-21 at 10:43 +0100, Michael Tremer wrote:
> Hi,
> 
> Just to clarify this: Do we need it for software to function or is it
> a nice to have?
I just tested sendEmail with this combination (IO-Socket-SSL and Net-
SSLeay) where it was needed while those tests.

> 
> The update has already been on the servers, but since we broke so
> many things we had to revert the patches and build it again. About
> four times by now. Poor Arne. Therefore I hope that we can avoid
> building it for a fifth time.
Understandable, am really not sure what else depends on the combination
with IO-Socket-SSL and Net-SSLeay, the git send-email problem for
example needed only an updated IO-Socket-SSL . The only problem i have
encountered without an updated Net-SSLeay was with sendEmail (IPFire
addon). There was also the explanaition from Cpan which i´ve posted in
the IO-Socket-SSL patch conversation. That´s why i´d send this patch
here too.

So i haven´t recognized malfunctioning in the core structure of IPFire
until now but am also not using all components. Difficult to say from
my side if it is really needed or if it can may wait until the next
core update...

> 
> Best,
> -Michael

Best,

Erik

> 
> > On 20 Oct 2019, at 15:39, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi all,
> > it seems that the updated IO-Socket-SSL also needs this updated
> > version
> > of Net-SSLeay. Have tested sendEmail with an updated IO-Socket-SSL
> > only
> > and it did not worked. After Net-SSLeay has also been updated
> > sendEMail
> > worked again. Am not sure which system components depends on an
> > updated
> > of those moduls too.
> > 
> > It might be may an idea to add this update to the core 137 update
> > since
> > the new version of IO-Socket-SSL has been already included with
> > Core
> > 136.
> > 
> > Best,
> > 
> > Erik
> > 
> > 
> > On Mi, 2019-09-25 at 14:25 +0100, Michael Tremer wrote:
> > > Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> > > 
> > > > On 25 Sep 2019, at 11:05, Erik Kapfer <ummeegge(a)ipfire.org>
> > > > wrote:
> > > > 
> > > > Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> > > > ---
> > > > config/rootfiles/common/Net_SSLeay | 1 -
> > > > lfs/Net_SSLeay                     | 6 +++---
> > > > 2 files changed, 3 insertions(+), 4 deletions(-)
> > > > 
> > > > diff --git a/config/rootfiles/common/Net_SSLeay
> > > > b/config/rootfiles/common/Net_SSLeay
> > > > index 4f14b74a7..bba719b03 100644
> > > > --- a/config/rootfiles/common/Net_SSLeay
> > > > +++ b/config/rootfiles/common/Net_SSLeay
> > > > @@ -4,7 +4,6 @@ usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-
> > > > thread-multi/Net/SSLeay.pm
> > > > usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/Net/SSLeay/Handle.pm
> > > > #usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay
> > > > #usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay/.packlist
> > > > -#usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay/SSLeay.bs
> > > > usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay/SSLeay.so
> > > > usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay/autosplit.ix
> > > > usr/lib/perl5/site_perl/5.30.0/MACHINE-linux-thread-
> > > > multi/auto/Net/SSLeay/debug_read.al
> > > > diff --git a/lfs/Net_SSLeay b/lfs/Net_SSLeay
> > > > index 90c0a310a..762bf1f4a 100644
> > > > --- a/lfs/Net_SSLeay
> > > > +++ b/lfs/Net_SSLeay
> > > > @@ -1,7 +1,7 @@
> > > > ###############################################################
> > > > ####
> > > > ############
> > > > #                                                              
> > > >     
> > > >           #
> > > > # IPFire.org - A linux based
> > > > firewall                                         #
> > > > -# Copyright (C) 2007-2018  IPFire Team  <info(a)ipfire.org>     
> > > >     
> > > >            #
> > > > +# Copyright (C) 2007-2019  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.82
> > > > +VER        = 1.88
> > > > 
> > > > THISAPP    = Net-SSLeay-$(VER)
> > > > DL_FILE    = $(THISAPP).tar.gz
> > > > @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> > > > 
> > > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> > > > 
> > > > -$(DL_FILE)_MD5 = 2170469d929d5173bacffd0cb2d7fafa
> > > > +$(DL_FILE)_MD5 = fcef4985f5f7e0381e3dddd0ee7878d1
> > > > 
> > > > install : $(TARGET)
> > > > 
> > > > -- 
> > > > 2.12.2
> > > > 
> > > 
> > > 
> 
> 


  reply	other threads:[~2019-10-21 11:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 10:05 Erik Kapfer
2019-09-25 13:25 ` Michael Tremer
2019-10-20 14:39   ` ummeegge
2019-10-21  9:43     ` Michael Tremer
2019-10-21 11:14       ` ummeegge [this message]
2019-10-22 11:39         ` Michael Tremer
2019-10-22 14:32           ` ummeegge
2019-10-22 14:33           ` ummeegge
2019-10-23  9:14             ` Michael Tremer
2019-10-24 13:57               ` ummeegge
2019-10-24 15:24                 ` 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=1be42b28fe36567546d95fb26c5dc4cecab4971e.camel@ipfire.org \
    --to=ummeegge@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