Skip Menu |

This queue is for tickets about the IO-Socket-SSL CPAN distribution.

Report information
The Basics
Id: 131384
Status: resolved
Priority: 0/
Queue: IO-Socket-SSL
People
Owner: Nobody in particular
Requestors: kiskele [...] krc.hu
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue Jan 07 06:40:30 2020 kiskele [...] krc.hu - Ticket created
Subject: ip_in_cn not working with IPv6 address
Hi I found some issues with IO::Socket::SSL when we are adding IPv6 address to Common Name of the certificate. if ( $identity eq $commonName ) { return 1 if $scheme->{ip_in_cn} == 4 ? length($ipn) == 4 : $scheme->{ip_in_cn} == 6 ? length($ipn) == 8 : 1; } 1. Here ip_in_cn == 1 is not handled. 2. length($ipn) is 16 byte in case of IPv6. Best Regards, Tamas Kelemen
  Mon Jan 13 04:34:56 2020 Steffen_Ullrich [...] genua.de - Correspondence added
Am Di 07. Jan 2020, 06:40:30, kiskele@krc.hu schrieb: Show quoted text
> Hi > > I found some issues with IO::Socket::SSL when we are adding IPv6 > address to Common Name of the certificate.
Thanks for your report. You are right regarding IPv6 - I've fixed this in commit 86f80e5. As for ip_in_cn == 1 - this case should be implicitly handled already and should behave as documented (i.e. it does not need to be 1, can only be 5 etc, only 4 and 6 have special meanings). Regards, Steffen
  Mon Jan 13 04:34:57 2020 The RT System itself - Status changed from 'new' to 'open'
  Mon Jan 13 04:34:57 2020 Steffen_Ullrich [...] genua.de - Status changed from 'open' to 'resolved'