Does anybody have the HAProxy software with version 1.5+ that runs on SUN Solaris 5.10 ? It will be used as reverse proxy server.
You can find an HAproxy package on the OpenCSW site.
https://www.opencsw.org/packages/haproxy/
Looks like version 1.6.9 is available
Related
In Live server we have perl version 5.6.1,recently we have enabled TLS 1.2 which resulted in a error "500 SSL Negotiation failed". Earlier we have TLS 1.0 we don't have any issues. Enabling TLS 1.2 is unavoidable which is mandatory. How to resolve this issue?
I have searched & found that SOAP-LITE module has to be installed in order to resolve the above issue but the version 5.6.1 does not support SOAP-LITE module. It is available in active perl 5.8 and above version. Is it adviseable to upgrade to 5.8 version inorder to install soap::Lite?
I have used the modules MSSQL::DBLIB and MSSQL::SQLLIB in this project, Will upgrade supports this module?
Given how old your version of Perl is it is very likely that your version of OpenSSL (which is used at the end for SSL connectivity in Perl) is as old too. Support for TLS 1.2 was added with OpenSSL 1.0.1 which was released 2012. Perl 5.6.1 was released in 2000 while in 2012 we already had Perl 5.14.
And it is not unlikely that the rest of your software is similar outdated and unsupported and likely insecure too.
How to resolve this issue?
Finally upgrade your long unsupported software stack. You can try to only update openssl and rebuild Crypt::SSLeay (likely no Net::SSLeay is used yet) to keep changes minimal but I'm not sure that this will work or even compile.
I am a perl developer and have been working on a ServiceNow API to create change tickets. It has been working well until this past Friday when ServiceNow depreciated support for TLS 1.0 and 1.1. My version of Perl is 5.8 so it's quite old. Are there any quick Perl 5.8 fixes?
Here are the perl modules I'm using.
use MIME::Base64;
use HTTP::Proxy;
use JSON;
use REST::Client;
the new errors;
Response: 500 SSL negotiation failed:
Response status: 500 Header: Content-Type=text/plain Header: Client-Date=Fri, 10 Jan 2020 23:06:10 GMT Header: Client-Warning=Internal response 500 SSL negotiation failed:
If you have any say in this you should really, really, really, really, really update your Perl. I mean, really. 5.8 is ancient.
If you cannot do that, you must at least update the piece of code that handles the TLS to a version >= 1.2 (Good luck!). Rest::Client uses LWP::UserAgent which in turn uses either Net::SSL or IO::Socket::SSL (I think) for the SSL stuff. If both are present Net::SSL will be used.
So you must investigate which one(s) you have and update one of them. Net::SSL is probably your best bet, since it is just a wrapper around the c library openssl (apt!). The other one probably has a rats tail of dependencies, but I didn't look.
Perl 5.8.0 is from July 2002. Perl 5.8.8 (which is what I suspect you are actually using) is from January 2006. Both of these are ancient versions and I highly recommend not using them.
I realise that you're using a specific version of an operating system (I'd guess RHEL5) and that upgrading your OS is a project that your company aren't going to want to undertake. But this is why we don't use the system installed version of Perl.
You have a few options.
Install another version of Perl alongside the system Perl. Put it in /opt/perl or somewhere like that. Make it a recent version and install a completely new library of modules for it. perlbrew is one nice way to achieve this.
Use a virtual machine or, better, a Docker container to host your API. That can be a newer OS, running a newer version of Perl with a newer version of the system libraries (which you're probably going to need - as your older version of openssl probably doesn't support TLS 1.2).
Stop using legacy hardware to host your project and move it into a cloud provider like AWS.
You either need to be more agile about updating your OS (which very few companies are very good at) or you need to separate your application's runtime environment from the underlying OS. That second route is what switched-on projects have been doing for several years now.
Godaddy supplies perl 5.8 on the "standard" unix share. Before attempting to use Dancer2 I would like to know if 5.8 will suffice.
Thank you.
A GoDaddy-wise comment: if you are trying to do this on a GoDaddy-hosted server and aren't running a dedicated server, it is doubtful they will upgrade the version of perl installed there on demand.
I have decided to install Cloudmin GPL for XEN in CentOS Server with 64 bit and my server configuration is Hard Disk : 4TB latest Xeon processor. The Scripts download from the URL :
http://cloudmin.virtualmin.com/gpl/scripts/cloudmin-gpl-redhat-install.sh
Which version can support for this.
Note: The CentOS 5.6 with 64 bit version does not support.
I have tested the script
http://cloudmin.virtualmin.com/gpl/scripts/cloudmin-gpl-redhat-install.sh
it's working fine and also you need to configure few things,
yum install birdge-utils*
for more help : https://www.virtualmin.com/documentation/cloudmin/virtualization/xen
I want to use Apache Thrift in Redhat and Fedora . Are there some known issues in using it in these platforms as the doc says only CentOS and Ubuntu
RedHat and Centos are almost identical platforms and Apache Thrift works well on both. Fedora is also very similar to the prior distros with the benefit of more modern packages and addons, and Apache Thrift also runs well there.