Hi Kess, Hi Fulltilt,
I've been dealing with this issue for a while taking info from this forum, thanks to everybody for the advice.
I've been using i-MSCP for a while but know almost nothing about its coding, let alone modifying it. So I'd like to clarify a bit.
My setup: Debian 9 + i-MSCP 1.5.3 2018120800
1/ Do I still need the snapd solution from Kess before applying this latest fix?
Edit: I've re-read and think I still need to do the snaps solution first.
2/ I found that the line number in the latest code match /var/www/imscp/engine/PerlLib/iMSCP/OpenSSL.pm from the maintenance branch not the stable release.
Does this mean I should replace just the OpenSSL.pm file with the maintenance brand (plus the code) or do I need other files (which ones) too?
3/ There're some extra lines above and below the #BEBIN and #END: tag. Do I need to keep them?
- ...
- my $cmd = [
- 'openssl', 'verify',
- ( ( $self->{'ca_bundle_container_path'} ne '' ) ? ( '-CAfile', $self->{'ca_bundle_container_path'} ) : () ),
- '-purpose', 'sslserver', $self->{'certificate_container_path'}
- ];
- my $rs = execute( $cmd, \ my $stdout, \ my $stderr );
- debug( $stdout ) if $stdout;
- error( sprintf(
- "SSL certificate is not valid: %s",
- ( $stderr || $stdout || 'Unknown error' ) =~ s/$self->{'certificate_container_path'}:\s+//r
- )) if $rs;
-
- # Begin :
- ...
- # END :
-
- $self->{'ca_bundle_container_path'} = '' unless $caBundle;
- $rs;
- }
Display More
Sorry if my questions sound a bit stupid, I just want to be sure. This issue has given me a lot of headaches recently.
Thank you,
Tony.