public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
* git send-email Undefined subroutine &IO::Socket::SSL
@ 2019-09-17  4:54 ummeegge
  2019-09-17 13:39 ` Michael Tremer
  0 siblings, 1 reply; 11+ messages in thread
From: ummeegge @ 2019-09-17  4:54 UTC (permalink / raw)
  To: development

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

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


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-17  4:54 git send-email Undefined subroutine &IO::Socket::SSL ummeegge
@ 2019-09-17 13:39 ` Michael Tremer
  2019-09-17 14:17   ` ummeegge
  0 siblings, 1 reply; 11+ messages in thread
From: Michael Tremer @ 2019-09-17 13:39 UTC (permalink / raw)
  To: development

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

Is this on IPFire or what distribution are you using here?

Looks like a bug in the perl module. Core Update 136 comes with an updated perl. Do you have that installed?

-Michael

> 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
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-17 13:39 ` Michael Tremer
@ 2019-09-17 14:17   ` ummeegge
  2019-09-17 20:05     ` Michael Tremer
  0 siblings, 1 reply; 11+ messages in thread
From: ummeegge @ 2019-09-17 14:17 UTC (permalink / raw)
  To: development

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

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 ?

> 
> -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
> > 
> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-17 14:17   ` ummeegge
@ 2019-09-17 20:05     ` Michael Tremer
  2019-09-18  5:01       ` ummeegge
  0 siblings, 1 reply; 11+ messages in thread
From: Michael Tremer @ 2019-09-17 20:05 UTC (permalink / raw)
  To: development

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

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
>>> 
>> 
>> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-17 20:05     ` Michael Tremer
@ 2019-09-18  5:01       ` ummeegge
  2019-09-18 12:29         ` Michael Tremer
  0 siblings, 1 reply; 11+ messages in thread
From: ummeegge @ 2019-09-18  5:01 UTC (permalink / raw)
  To: development

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

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
> > > > 
> > > 
> > > 
> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-18  5:01       ` ummeegge
@ 2019-09-18 12:29         ` Michael Tremer
  2019-09-18 12:57           ` ummeegge
  0 siblings, 1 reply; 11+ messages in thread
From: Michael Tremer @ 2019-09-18 12:29 UTC (permalink / raw)
  To: development

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

Hi,

No this looks like an FTP connection issue, but we don’t use FTP.

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
>>>>> 
>>>> 
>>>> 
>> 
>> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-18 12:29         ` Michael Tremer
@ 2019-09-18 12:57           ` ummeegge
  2019-09-19 13:14             ` Michael Tremer
  0 siblings, 1 reply; 11+ messages in thread
From: ummeegge @ 2019-09-18 12:57 UTC (permalink / raw)
  To: development

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

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.

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
> > > > > > 
> > > > > 
> > > > > 
> > > 
> > > 
> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-18 12:57           ` ummeegge
@ 2019-09-19 13:14             ` Michael Tremer
  2019-09-19 14:34               ` ummeegge
  2019-09-19 16:22               ` fail2ban false positives on people01.haj.ipfire.org (was: Re: git send-email Undefined subroutine &IO::Socket::SSL) peter.mueller
  0 siblings, 2 replies; 11+ messages in thread
From: Michael Tremer @ 2019-09-19 13:14 UTC (permalink / raw)
  To: development

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

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?

Peter has installed fail2ban this week and maybe that is a little bit too… err.. secure now?!

-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
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>> 
>> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-19 13:14             ` Michael Tremer
@ 2019-09-19 14:34               ` ummeegge
  2019-09-23 22:33                 ` Michael Tremer
  2019-09-19 16:22               ` fail2ban false positives on people01.haj.ipfire.org (was: Re: git send-email Undefined subroutine &IO::Socket::SSL) peter.mueller
  1 sibling, 1 reply; 11+ messages in thread
From: ummeegge @ 2019-09-19 14:34 UTC (permalink / raw)
  To: development

[-- 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
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > 
> > > 
> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* fail2ban false positives on people01.haj.ipfire.org (was: Re: git send-email Undefined subroutine &IO::Socket::SSL)
  2019-09-19 13:14             ` Michael Tremer
  2019-09-19 14:34               ` ummeegge
@ 2019-09-19 16:22               ` peter.mueller
  1 sibling, 0 replies; 11+ messages in thread
From: peter.mueller @ 2019-09-19 16:22 UTC (permalink / raw)
  To: development

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

Hello Erik, hello Michael, hello *,

thank you for reporting fail2ban being too restrictive on SSH
service running at people01. It is now configured to be more
relaxed and blocking IP addresses for a shorter amount of time.

I do not expect any troubles with these settings, except for
extremely sloppy users. :-) However, they are too relaxed in
my point of view, and I would like to raise them back to old values
some day.

Besides typos entering passwords - which unfortunately is a
backside of running Kerberos, SSH access with public keys is
somewhat breaking that design -, I cannot really imagine of
other authentication failures for legitimate users.

If possible, I would like to ask anybody who has SSH access
on people.ipfire.org to clean up their SSH settings, i.e. drop
old keys which are not being used anymore. Let me know if I
have overlooked something.

Thanks, and best regards,
Peter Müller

P.S.: Fail2ban is still active with more strict configuration
for Submissions and IMAPS, haven't heard any complaints there
so far...

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: git send-email Undefined subroutine &IO::Socket::SSL
  2019-09-19 14:34               ` ummeegge
@ 2019-09-23 22:33                 ` Michael Tremer
  0 siblings, 0 replies; 11+ messages in thread
From: Michael Tremer @ 2019-09-23 22:33 UTC (permalink / raw)
  To: development

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

Hi,

> On 19 Sep 2019, at 15:34, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> 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 ?! 

If sendEmail is being unmaintained it has to be removed.

There is no point in carrying around something that does not work or is expected 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.

> 
> 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 ?

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.

> 
> 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


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2019-09-23 22:33 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-17  4:54 git send-email Undefined subroutine &IO::Socket::SSL ummeegge
2019-09-17 13:39 ` Michael Tremer
2019-09-17 14:17   ` ummeegge
2019-09-17 20:05     ` Michael Tremer
2019-09-18  5:01       ` ummeegge
2019-09-18 12:29         ` Michael Tremer
2019-09-18 12:57           ` ummeegge
2019-09-19 13:14             ` Michael Tremer
2019-09-19 14:34               ` ummeegge
2019-09-23 22:33                 ` Michael Tremer
2019-09-19 16:22               ` fail2ban false positives on people01.haj.ipfire.org (was: Re: git send-email Undefined subroutine &IO::Socket::SSL) peter.mueller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox