Re: git send-email Undefined subroutine &IO::Socket::SSL

[ummeegge <ummeegge@ipfire.org>]

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

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´t 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 ?! 

Was digging also a little around and found this Bug -->
https://rt.cpan.org/Public/Bug/Display.html?id=126899
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.

Might this also be a candidate for the upcoming realease ?

On Do, 2019-09-19 at 09:14 -0400, Michael Tremer wrote:
> Hi,
> 
> > On 18 Sep 2019, at 08:57, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi Michael,
> > 
> > On Mi, 2019-09-18 at 08:29 -0400, Michael Tremer wrote:
> > > Hi,
> > > 
> > > No this looks like an FTP connection issue, but we don’t use FTP.
> > 
> > Have used SFTP like in earlier times with FilZilla -->
> > 
> > fzSftp started, protocol_version=8
> > 
> > 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´s happend.
> 
> 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.

> 
> Peter has installed fail2ban this week and maybe that is a little bit
> too… 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.

Best,

Erik

> 
> -Michael
> 
> > 
> > Best,
> > 
> > Erik
> > 
> > > 
> > > What did you use to upload this file?
> > > 
> > > -Michael
> > > 
> > > > On 18 Sep 2019, at 01:01, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > > 
> > > > Hi Michael,
> > > > have currently a problem to upload the IO-Socket-SSL sources to
> > > > the
> > > > pub
> > > > directory.
> > > > The log says:
> > > > 
> > > > 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" 
> > > > "IO-Socket-SSL-2.066.tar.gz"
> > > > Befehl:	local:/home/neptun/Downloads/IO-Socket-SSL-
> > > > 2.066.tar.gz 
> > > > => remote:/pub/sources/source-2.x/IO-Socket-SSL-2.066.tar.gz
> > > > Fehler:	Zeitüberschreitung der Verbindung nach 20 Sekunden
> > > > Inaktivität
> > > > Fehler:	Dateiübertragung fehlgeschlagen
> > > > Status:	Verbindung zum Server getrennt
> > > > 
> > > > May a permission problem ?
> > > > 
> > > > IO-Socket-SSL update patch has been send.
> > > > 
> > > > Best,
> > > > 
> > > > Erik
> > > > 
> > > > 
> > > > On Di, 2019-09-17 at 16:05 -0400, Michael Tremer wrote:
> > > > > Hi,
> > > > > 
> > > > > > On 17 Sep 2019, at 10:17, ummeegge <ummeegge(a)ipfire.org>
> > > > > > wrote:
> > > > > > 
> > > > > > Hi Michael,
> > > > > > 
> > > > > > On Di, 2019-09-17 at 09:39 -0400, Michael Tremer wrote:
> > > > > > > Is this on IPFire or what distribution are you using
> > > > > > > here?
> > > > > > 
> > > > > > Yes, the basis system is IPFire.
> > > > > > 
> > > > > > > 
> > > > > > > Looks like a bug in the perl module. Core Update 136
> > > > > > > comes
> > > > > > > with
> > > > > > > an
> > > > > > > updated perl. Do you have that installed?
> > > > > > 
> > > > > > 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 ?
> > > > > 
> > > > > 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.
> > > > > 
> > > > > Best,
> > > > > -Michael
> > > > > 
> > > > > > 
> > > > > > > 
> > > > > > > -Michael
> > > > > > > 
> > > > > > 
> > > > > > Best,
> > > > > > 
> > > > > > Erik
> > > > > > 
> > > > > > > > On 17 Sep 2019, at 00:54, ummeegge <ummeegge(a)ipfire.org
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > > 
> > > > > > > > Hi all,
> > > > > > > > i wanted to report a porblem with git send-email. I
> > > > > > > > currently
> > > > > > > > get a
> > > > > > > > 
> > > > > > > > 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.
> > > > > > > > 
> > > > > > > > if i try to send patches to the mailinglist. The email
> > > > > > > > setup
> > > > > > > > is configured like explained in the wiki
> > > > > > > > 
> > > > > > > > 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
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Best,
> > > > > > > > 
> > > > > > > > Erik
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > 
> > > 
> 
>