From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer <michael.tremer@ipfire.org> To: development@lists.ipfire.org Subject: Re: git send-email Undefined subroutine &IO::Socket::SSL Date: Mon, 23 Sep 2019 23:33:51 +0100 Message-ID: <A8A93CE5-F26A-4E9E-9B97-C9872B23B532@ipfire.org> In-Reply-To: <c8e0cb50113673db5e9903feaedd0d219a9ead0f.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1695984530410197575==" List-Id: <development.lists.ipfire.org> --===============1695984530410197575== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > On 19 Sep 2019, at 15:34, ummeegge <ummeegge(a)ipfire.org> wrote: >=20 > Hello, > have found another one which might be related to the IO-Socket-SSL > module. sendEmail currently do not works, in fact the project is dead > (last version from 2009) even there are some patches from Debian/Ubuntu > around for it which i haven=C2=B4t tried until now, but am not sure if it > might not be the best to drop sendEmail and replace it by another > lightweight SMTP client if desired ?!=20 If sendEmail is being unmaintained it has to be removed. There is no point in carrying around something that does not work or is expec= ted to break at any minute. If people have given up on it, we cannot maintain= all sorts of code for them since we only have limited resources, too. However, I would not want to add another mailer, because we already have dma = which can be nicely configured using the web user interface. >=20 > Was digging also a little around and found this Bug --> > https://rt.cpan.org/Public/Bug/Display.html?id=3D126899 > if TLSv1.3 should be used. As far as i understand 'Net-SSLeay' needs > also to be updated if TLSv1.3 should be usable with IO-Socket-SSL. > IPFire delivers currently 'Net-SSLeay-1.82' according to this --> > https://metacpan.org/pod/Net::SSLeay TLSv1.3 is only supported with > 'Net-SSLeay-1.86' . Have currently no misfunctionality realized but am > an update for Net-SSLeay runs here currently too. >=20 > Might this also be a candidate for the upcoming realease ? Not necessarily for the release, because this is not a bug. But definitely send a patch because we should be able to use TLS 1.3 for all = perl programs, too. >=20 > On Do, 2019-09-19 at 09:14 -0400, Michael Tremer wrote: >> Hi, >>=20 >>> On 18 Sep 2019, at 08:57, ummeegge <ummeegge(a)ipfire.org> wrote: >>>=20 >>> Hi Michael, >>>=20 >>> On Mi, 2019-09-18 at 08:29 -0400, Michael Tremer wrote: >>>> Hi, >>>>=20 >>>> No this looks like an FTP connection issue, but we don=E2=80=99t use FTP. >>>=20 >>> Have used SFTP like in earlier times with FilZilla --> >>>=20 >>> fzSftp started, protocol_version=3D8 >>>=20 >>> Login and navigation was possible but no upload. >>> Was nevertheless able to upload now the IO-Socket-SSL sources via >>> console on a Linux Mint system. >>> There seems to be some new really sharp settings on SSH, my IP has >>> been >>> two times banned where i am not 100% sure why that=C2=B4s happend. >>=20 >> Since when is that? > Since i have had a little break with sending patches the time span > might not be accurate but i recognize it yesterday by sending in the > IO-Socket-SSL patch. >=20 >>=20 >> Peter has installed fail2ban this week and maybe that is a little bit >> too=E2=80=A6 err.. secure now?! > :-) . No problem, needed to reconnect to get a new IP and was then able > to deliver it via console but FileZilla seems to be a little unloved. >=20 > Best, >=20 > Erik >=20 >>=20 >> -Michael >>=20 >>>=20 >>> Best, >>>=20 >>> Erik >>>=20 >>>>=20 >>>> What did you use to upload this file? >>>>=20 >>>> -Michael >>>>=20 >>>>> On 18 Sep 2019, at 01:01, ummeegge <ummeegge(a)ipfire.org> wrote: >>>>>=20 >>>>> Hi Michael, >>>>> have currently a problem to upload the IO-Socket-SSL sources to >>>>> the >>>>> pub >>>>> directory. >>>>> The log says: >>>>>=20 >>>>> Status: Verbinde mit git.ipfire.org... >>>>> Status: Connected to fw01.ipfire.org >>>>> Status: Starte Upload von /home/neptun/Downloads/IO-Socket-SSL- >>>>> 2.066.tar.gz >>>>> Befehl: cd "/pub/sources/source-2.x" >>>>> Antwort: New directory is: "/pub/sources/source-2.x" >>>>> Befehl: put "/home/neptun/Downloads/IO-Socket-SSL- >>>>> 2.066.tar.gz"=20 >>>>> "IO-Socket-SSL-2.066.tar.gz" >>>>> Befehl: local:/home/neptun/Downloads/IO-Socket-SSL- >>>>> 2.066.tar.gz=20 >>>>> =3D> remote:/pub/sources/source-2.x/IO-Socket-SSL-2.066.tar.gz >>>>> Fehler: Zeit=C3=BCberschreitung der Verbindung nach 20 Sekunden >>>>> Inaktivit=C3=A4t >>>>> Fehler: Datei=C3=BCbertragung fehlgeschlagen >>>>> Status: Verbindung zum Server getrennt >>>>>=20 >>>>> May a permission problem ? >>>>>=20 >>>>> IO-Socket-SSL update patch has been send. >>>>>=20 >>>>> Best, >>>>>=20 >>>>> Erik >>>>>=20 >>>>>=20 >>>>> On Di, 2019-09-17 at 16:05 -0400, Michael Tremer wrote: >>>>>> Hi, >>>>>>=20 >>>>>>> On 17 Sep 2019, at 10:17, ummeegge <ummeegge(a)ipfire.org> >>>>>>> wrote: >>>>>>>=20 >>>>>>> Hi Michael, >>>>>>>=20 >>>>>>> On Di, 2019-09-17 at 09:39 -0400, Michael Tremer wrote: >>>>>>>> Is this on IPFire or what distribution are you using >>>>>>>> here? >>>>>>>=20 >>>>>>> Yes, the basis system is IPFire. >>>>>>>=20 >>>>>>>>=20 >>>>>>>> Looks like a bug in the perl module. Core Update 136 >>>>>>>> comes >>>>>>>> with >>>>>>>> an >>>>>>>> updated perl. Do you have that installed? >>>>>>>=20 >>>>>>> Yes, the build system runs on core 136. Have updated IO- >>>>>>> Socket- >>>>>>> SSL >>>>>>> now >>>>>>> to version 2.066 --> >>>>>>> https://metacpan.org/pod/IO::Socket::SSL >>>>>>> and it seems to work now. Should i send the update tooto >>>>>>> the >>>>>>> list ? >>>>>>=20 >>>>>> Yes, can you do this very swiftly because I think we might >>>>>> want >>>>>> to >>>>>> consider to re-open Core Update 136 and include this patch if >>>>>> there >>>>>> are more problems being caused by it. >>>>>>=20 >>>>>> Best, >>>>>> -Michael >>>>>>=20 >>>>>>>=20 >>>>>>>>=20 >>>>>>>> -Michael >>>>>>>>=20 >>>>>>>=20 >>>>>>> Best, >>>>>>>=20 >>>>>>> Erik >>>>>>>=20 >>>>>>>>> On 17 Sep 2019, at 00:54, ummeegge <ummeegge(a)ipfire.org >>>>>>>>>>=20 >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>> Hi all, >>>>>>>>> i wanted to report a porblem with git send-email. I >>>>>>>>> currently >>>>>>>>> get a >>>>>>>>>=20 >>>>>>>>> Send this email? ([y]es|[n]o|[q]uit|[a]ll): y >>>>>>>>> Undefined subroutine >>>>>>>>> &IO::Socket::SSL::set_client_defaults >>>>>>>>> called >>>>>>>>> at /usr/libexec/git-core/git-send-email line 1371. >>>>>>>>>=20 >>>>>>>>> if i try to send patches to the mailinglist. The email >>>>>>>>> setup >>>>>>>>> is configured like explained in the wiki >>>>>>>>>=20 >>>>>>>>> git config --global sendemail.smtpencryption ssl >>>>>>>>> git config --global sendemail.smtpserver >>>>>>>>> submissions.ipfire.org >>>>>>>>> git config --global sendemail.smtpserverport 465 >>>>>>>>> git config --global sendemail.smtpuser USERNAME >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Best, >>>>>>>>>=20 >>>>>>>>> Erik --===============1695984530410197575==--