I was cleaning out my email folder yesterday and I came across this old email. While I have removed anything that would specify who this email is with the results are still proving of CLDMV’s systems. I’m also pretty sure this email was prior to the double compression PNG system we currently use now.


More good news.. Here is the report from google on image compression:
Losslessly compressing image/cache/data/ServiceRepairEvinrude-180x350.png could save 22.9KiB (57% reduction). 
Losslessly compressing image/cache/data/ServiceRepairMercury-180x350.png could save 21.2KiB (61% reduction). 
Losslessly compressing image/cache/data/free_shipping_smlbnnr-550x62.png could save 12.2KiB (61% reduction)

Here are the results from optimizing them in my system:
Processed file: image/cache/data/ServiceRepairEvinrude-180x350.png 10 times (60.49%).
Processed file: image/cache/data/ServiceRepairMercury-180x350.png 2 times (62.61%).
Processed file: image/cache/data/free_shipping_smlbnnr-550x62.png 2 times (62.39%).

More good news.. Here is the report from google on image compression:

Losslessly compressing image/cache/data/ServiceRepairEvinrude-180x350.png could save 22.9KiB (57% reduction).

Losslessly compressing image/cache/data/ServiceRepairMercury-180x350.png could save 21.2KiB (61% reduction).

Losslessly compressing image/cache/data/free_shipping_smlbnnr-550x62.png could save 12.2KiB (61% reduction)

Here are the results from optimizing them in my system:

Processed file: image/cache/data/ServiceRepairEvinrude-180x350.png 10 times (60.49%).

Processed file: image/cache/data/ServiceRepairMercury-180x350.png 2 times (62.61%).

Processed file: image/cache/data/free_shipping_smlbnnr-550x62.png 2 times (62.39%).

As you can see from above not only did our system compress the images as much as Google said we could. But we were able to compress 1-4% more. Here is a recent daily report of our image compression system.


[/www/blog.example.net/html] 230 files optimized at 48.35% overall rate.
[/www/example.net/html] 12 files optimized at 40.46% overall rate.

[/www/blog.example.net/html] 230 files optimized at 48.35% overall rate.

[/www/example.net/html] 12 files optimized at 40.46% overall rate.

Keeping in mind all the compression is done lossless. Meaning there is no loss in visual quality. The only downside to the compression is if the images store data such as where they were taken, that data is removed.

New Security Features

May 12, 2014

Nathaniel Hyson

Information Security Servers Why CLDMV No Comments

Previously we had been using the over-popular Fail2Ban to scan our logs as a temporary fix for the issue. While the anti-DDOS software written by CLDMV takes care of a ton of bans every day. The hacking attempts are still being attempted by some what smarter hackers.

Today we rolled out our first module for log scanning. With SSH probably being the #1 threat to servers out there that is what we chose to target for our scanner. Took several days but the results are amazing. While I can’t divulge the inner workings of the module. Let me just show you the first ban email we got after running it for the first time:


Banned 29 ips:
115.238.236.84 for 3 weeks, 2 days, 9 hours
116.10.191.170 for 2 weeks, 6 days, 6 hours
116.10.191.171 for 2 weeks, 6 days, 1 hour, 20 minutes
116.10.191.178 for 3 weeks, 14 hours, 24 minutes
116.10.191.181 for 7 weeks, 3 days, 19 hours, 12 minutes
116.10.191.183 for 1 week, 5 days
116.10.191.190 for 1 week, 4 days, 15 hours, 29 minutes, 1 second
116.10.191.198 for 3 weeks, 4 days
116.10.191.199 for 7 weeks, 1 day
116.10.191.202 for 6 weeks, 6 days
116.10.191.206 for 2 weeks, 6 days, 14 hours, 31 minutes, 34 seconds
116.10.191.213 for 2 weeks, 1 day, 3 hours, 47 minutes, 57 seconds
116.10.191.215 for 4 weeks, 4 days, 15 hours, 54 minutes, 23 seconds
116.10.191.220 for 6 weeks, 6 days, 9 hours, 35 minutes, 59 seconds
116.10.191.229 for 12 weeks, 2 days, 53 minutes, 20 seconds
116.10.191.232 for 4 weeks, 4 days, 3 hours
116.10.191.236 for 1 week, 6 days, 12 hours
116.10.191.237 for 1 week, 6 days, 22 hours, 6 minutes, 18 seconds
116.10.191.239 for 4 weeks, 4 days
162.252.243.147 for 2 weeks, 1 day, 17 hours, 57 minutes, 16 seconds
211.154.150.135 for 8 weeks, 6 days, 19 minutes, 59 seconds
218.22.16.12 for 1 week, 4 days, 1 hour, 34 minutes, 53 seconds
219.138.135.64 for 1 week, 2 hours, 49 minutes, 24 seconds
222.163.192.154 for 3 weeks, 6 days, 2 hours, 22 minutes, 19 seconds
42.62.17.250 for 2 weeks, 5 days, 13 hours, 41 minutes, 59 seconds
61.174.49.111 for 6 days, 5 hours, 32 minutes, 18 seconds
61.174.51.215 for 8 weeks, 2 hours, 15 minutes, 59 seconds
61.174.51.217 for 1 week, 5 days, 16 hours, 22 minutes, 51 seconds
61.174.51.227 for 1 week, 6 days, 5 hours, 58 minutes, 59 seconds

Banned 29 ips:

115.238.236.84 for 3 weeks, 2 days, 9 hours

116.10.191.170 for 2 weeks, 6 days, 6 hours

116.10.191.171 for 2 weeks, 6 days, 1 hour, 20 minutes

116.10.191.178 for 3 weeks, 14 hours, 24 minutes

116.10.191.181 for 7 weeks, 3 days, 19 hours, 12 minutes

116.10.191.183 for 1 week, 5 days

116.10.191.190 for 1 week, 4 days, 15 hours, 29 minutes, 1 second

116.10.191.198 for 3 weeks, 4 days

116.10.191.199 for 7 weeks, 1 day

116.10.191.202 for 6 weeks, 6 days

116.10.191.206 for 2 weeks, 6 days, 14 hours, 31 minutes, 34 seconds

116.10.191.213 for 2 weeks, 1 day, 3 hours, 47 minutes, 57 seconds

116.10.191.215 for 4 weeks, 4 days, 15 hours, 54 minutes, 23 seconds

116.10.191.220 for 6 weeks, 6 days, 9 hours, 35 minutes, 59 seconds

116.10.191.229 for 12 weeks, 2 days, 53 minutes, 20 seconds

116.10.191.232 for 4 weeks, 4 days, 3 hours

116.10.191.236 for 1 week, 6 days, 12 hours

116.10.191.237 for 1 week, 6 days, 22 hours, 6 minutes, 18 seconds

116.10.191.239 for 4 weeks, 4 days

162.252.243.147 for 2 weeks, 1 day, 17 hours, 57 minutes, 16 seconds

211.154.150.135 for 8 weeks, 6 days, 19 minutes, 59 seconds

218.22.16.12 for 1 week, 4 days, 1 hour, 34 minutes, 53 seconds

219.138.135.64 for 1 week, 2 hours, 49 minutes, 24 seconds

222.163.192.154 for 3 weeks, 6 days, 2 hours, 22 minutes, 19 seconds

42.62.17.250 for 2 weeks, 5 days, 13 hours, 41 minutes, 59 seconds

61.174.49.111 for 6 days, 5 hours, 32 minutes, 18 seconds

61.174.51.215 for 8 weeks, 2 hours, 15 minutes, 59 seconds

61.174.51.217 for 1 week, 5 days, 16 hours, 22 minutes, 51 seconds

61.174.51.227 for 1 week, 6 days, 5 hours, 58 minutes, 59 seconds

Keep in mind these numbers and bans are simply based upon the past 24 hours of logs.

Update:

This guy takes the cake for CLDMV’s Anti-DDOS software catching a potential intrusion. Just received this email:


Banned 1 ip:
61.174.51.231 for 85 weeks, 5 days, 20 hours, 38 minutes, 42 seconds

Banned 1 ip:

61.174.51.231 for 85 weeks, 5 days, 20 hours, 38 minutes, 42 seconds

Also the log processing module for SMTP hackers is in place as well now. Here’s the first email for the past 24 hours of attempts:


Banned 36 ips:
1.22.172.138 for 28 weeks, 5 days, 5 hours, 21 minutes, 35 seconds
105.237.137.36 for 24 weeks, 4 days, 5 hours, 56 minutes
105.237.36.170 for 25 weeks, 4 hours, 15 minutes, 1 second
118.97.191.156 for 5 weeks, 1 day
119.147.213.144 for 5 weeks, 5 days, 12 hours
122.155.197.35 for 6 weeks, 6 days, 16 hours, 24 minutes, 4 seconds
151.8.99.194 for 18 weeks, 2 days, 9 hours, 29 minutes, 43 seconds
178.41.231.192 for 7 weeks, 6 days, 7 hours, 59 minutes, 59 seconds
180.166.96.38 for 2 weeks, 2 days, 4 hours, 47 minutes, 59 seconds
180.250.80.237 for 6 weeks, 6 days, 18 hours
182.73.180.210 for 1 week, 1 day
186.73.227.26 for 29 weeks, 6 days, 20 hours, 13 minutes, 43 seconds
190.5.230.178 for 14 weeks, 4 days, 15 hours, 59 minutes, 59 seconds
200.241.178.210 for 3 weeks, 1 day
200.80.106.38 for 1 week, 4 hours, 48 minutes
201.151.192.69 for 2 weeks, 4 days
201.27.5.102 for 2 days, 18 hours, 27 minutes, 41 seconds
202.191.206.242 for 3 weeks, 6 days
203.45.163.105 for 28 weeks, 3 days, 9 hours, 56 minutes, 33 seconds
212.156.27.62 for 6 weeks, 6 days
212.174.252.130 for 9 weeks, 1 day
212.75.134.12 for 4 weeks
213.186.183.252 for 5 weeks, 4 days, 15 hours, 59 minutes, 59 seconds
217.91.121.82 for 2 weeks, 6 days
37.159.188.90 for 7 weeks, 1 day
41.206.23.51 for 4 weeks, 2 days
50.245.73.14 for 9 weeks, 4 days, 12 hours
66.112.96.50 for 5 weeks, 1 day
66.188.229.156 for 7 weeks, 1 day
74.7.103.53 for 17 weeks, 1 day, 6 hours, 24 minutes
80.146.31.233 for 5 weeks, 1 day
85.152.57.61 for 2 days
85.40.63.218 for 14 weeks, 3 days, 3 hours, 27 minutes, 26 seconds
87.139.213.236 for 20 weeks, 22 hours, 23 minutes, 59 seconds
93.107.104.11 for 1 week, 6 days, 5 hours, 47 minutes, 35 seconds
94.145.37.72 for 15 weeks, 4 days, 6 hours

Banned 36 ips:

1.22.172.138 for 28 weeks, 5 days, 5 hours, 21 minutes, 35 seconds

105.237.137.36 for 24 weeks, 4 days, 5 hours, 56 minutes

105.237.36.170 for 25 weeks, 4 hours, 15 minutes, 1 second

118.97.191.156 for 5 weeks, 1 day

119.147.213.144 for 5 weeks, 5 days, 12 hours

122.155.197.35 for 6 weeks, 6 days, 16 hours, 24 minutes, 4 seconds

151.8.99.194 for 18 weeks, 2 days, 9 hours, 29 minutes, 43 seconds

178.41.231.192 for 7 weeks, 6 days, 7 hours, 59 minutes, 59 seconds

180.166.96.38 for 2 weeks, 2 days, 4 hours, 47 minutes, 59 seconds

180.250.80.237 for 6 weeks, 6 days, 18 hours

182.73.180.210 for 1 week, 1 day

186.73.227.26 for 29 weeks, 6 days, 20 hours, 13 minutes, 43 seconds

190.5.230.178 for 14 weeks, 4 days, 15 hours, 59 minutes, 59 seconds

200.241.178.210 for 3 weeks, 1 day

200.80.106.38 for 1 week, 4 hours, 48 minutes

201.151.192.69 for 2 weeks, 4 days

201.27.5.102 for 2 days, 18 hours, 27 minutes, 41 seconds

202.191.206.242 for 3 weeks, 6 days

203.45.163.105 for 28 weeks, 3 days, 9 hours, 56 minutes, 33 seconds

212.156.27.62 for 6 weeks, 6 days

212.174.252.130 for 9 weeks, 1 day

212.75.134.12 for 4 weeks

213.186.183.252 for 5 weeks, 4 days, 15 hours, 59 minutes, 59 seconds

217.91.121.82 for 2 weeks, 6 days

37.159.188.90 for 7 weeks, 1 day

41.206.23.51 for 4 weeks, 2 days

50.245.73.14 for 9 weeks, 4 days, 12 hours

66.112.96.50 for 5 weeks, 1 day

66.188.229.156 for 7 weeks, 1 day

74.7.103.53 for 17 weeks, 1 day, 6 hours, 24 minutes

80.146.31.233 for 5 weeks, 1 day

85.152.57.61 for 2 days

85.40.63.218 for 14 weeks, 3 days, 3 hours, 27 minutes, 26 seconds

87.139.213.236 for 20 weeks, 22 hours, 23 minutes, 59 seconds

93.107.104.11 for 1 week, 6 days, 5 hours, 47 minutes, 35 seconds

94.145.37.72 for 15 weeks, 4 days, 6 hours

Why CLDMV for hosting?

May 7, 2014

Nathaniel Hyson

Clients Information Servers Why CLDMV No Comments

On average our clients are seeing a 20-30% increase in page speeds from their old hosting environments to CLDMV’s Servers. Roughly a 40% decrease in the size of downloaded content as all CSS/JS is minified, users can minify their HTML if they choose to do so and all images are compresses to the maximin they can be (completely lossless compression of course).

So far all of our clients have came to us from their own dedicated servers where they were paying on average 300$/month for their servers. CLDMV’s clients pay on average 130$/month as of writing this post. While essentially our service is “Shared hosting on steroids” it can also be compared to a “no limit” VPS. Since most people who are running online websites grow out of their shared hosting environment within the first couple years of business (assuming traffic increases at a steady rate) they don’t want all the hassle of managing a server.

Often more times than not they pay 30-40$/month to have a commercial control panel installed and on top of that pay a system administrator to change things when needed. With CLDMV changes are only a call away and once the control panel rolls out many operations of the hosting plan will be available via the control panel (free of charge).

In our experience most clients running online websites simply need a faster website. They don’t need nor want an entire dedicated server. The industry has forced users to upgrade to that point due to over selling and over crowding servers. Here at CLDMV we monitor everything on the servers daily and apply upgrades or code changes to keep the system running smoothly. Client stats are tracked every hour, server stats every 15 minutes. Traffic is always instantly tracked (logged every 60 seconds). Our mission is to provide affordable hosting with all the benefits of a going out and hiring a optimization company to come and optimize your dedicated server. With CLDMV you don’t have to hire or pay for anything extra for your service.

With many options available (some not listed or posted about yet) the possibilities of hosting with CLDMV are endless. Need your own or want to use your own database server? We got your covered. Need load balancing? We can do that as well (though our biggest servers can handle over 1000 512MB php threads at any given instance and up to 10Gbps of transfer). Just want complete isolation? We offer dedicated servers as well where all the optimization and management of the server is done by us and you have a completely isolated part of our network.

Lets step back for a minute. Any hosting company can offer you the world but can they deliver? Do they have hard numbers which prove their service? Lets let the numbers talk for themselves. Below is a table of response time, load time, downloaded content (with a hard refresh to force all content to be downloaded), google page speed score and estimated cost if any idea of cost is available.

Site 1: http://beautyjoint.com

Site	Response Time	Load Time	Download (First Load)	Page Speed Score	Cost
Original	575ms	2.25s	900KB	66	1000$~
Compare	444ms	1.56s	627KB	86	200$~

Site 2: http://adrianas.1stwebstudio.com/en/

Site	Response Time	Load Time	Download (First Load)	Page Speed Score	Cost
Original	1.61s	7.00s	4.9MB	46	??
Compare	775ms	3.97s	3.6MB	86	130$~??

Site 3: http://www.extasybooks.com/

Site	Response Time	Load Time	Download (First Load)	Page Speed Score	Cost
Old	945ms	5.85s	1.1MBKB	74	600$~
Current	772ms	1.97s	627KB	88	300$~

Notes:

Site speeds and scores ran on 2014/05/07 at 4pm PST (for site 1 and site 2)

Links may or may not be valid at time of viewing.

Sites listed above have given permission to post these stats as a comparison of our service.

Minify HTML as a service

May 5, 2014

Nathaniel Hyson

Features Servers No Comments

While mileage may vary with minifying HTML it is not done automatically like minifying css and js. However there is a background service running for anyone wishing to use it on the server free of charge. Below is the php code to access the service.


function minifyhtml($html){
	$post = array(
		'html'	=> $html
	);
	$url = '127.0.0.1/minhtml.php';

	$ch = curl_init( $url );
	curl_setopt( $ch, CURLOPT_POST, 1);
	curl_setopt( $ch, CURLOPT_POSTFIELDS, http_build_query($_POST));
	curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
	curl_setopt($ch, CURLOPT_VERBOSE, 1);
	curl_setopt($ch, CURLOPT_HEADER, 1);
	$response = curl_exec( $ch );
	
	$header_size = curl_getinfo($ch, CURLINFO_HEADER_SIZE);
	$header = substr($response, 0, $header_size);
	$body = substr($response, $header_size);
	$headers = array();
	$tmp = explode("n",trim($header));
	foreach($tmp as $line){
		if (trim($line) != ''){
			if (strstr($line,':')){
				$line = explode(':',$line);
				$key = trim($line[0]);
				unset($line[0]);
				$line = trim(implode(':',$line));
				$headers[$key] = $line;
			}
		}
	}
	return array($body,$headers);
}

function minifyhtml($html){

$post = array(

'html' => $html

);

$url = '127.0.0.1/minhtml.php';

$ch = curl_init( $url );

curl_setopt( $ch, CURLOPT_POST, 1);

curl_setopt( $ch, CURLOPT_POSTFIELDS, http_build_query($_POST));

curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);

curl_setopt($ch, CURLOPT_VERBOSE, 1);

curl_setopt($ch, CURLOPT_HEADER, 1);

$response = curl_exec( $ch );

$header_size = curl_getinfo($ch, CURLINFO_HEADER_SIZE);

$header = substr($response, 0, $header_size);

$body = substr($response, $header_size);

$headers = array();

$tmp = explode("n",trim($header));

foreach($tmp as $line){

if (trim($line) != ''){

if (strstr($line,':')){

$line = explode(':',$line);

$key = trim($line[0]);

unset($line[0]);

$line = trim(implode(':',$line));

$headers[$key] = $line;

}

return array($body,$headers);

}

Combined with the above code you can use the below code to retrieve the minified html body as well as the original bytes, minified bytes, and saved percent by minifying the html.


list($body,$headers) = minifyhtml($src);
$srcBytes = $headers['X-SRCBytes'];
$minOutputBytes = $headers['X-OutputBytes'];
$savedPercent = $headers['X-SavedPercent'];

list($body,$headers) = minifyhtml($src);

$srcBytes = $headers['X-SRCBytes'];

$minOutputBytes = $headers['X-OutputBytes'];

$savedPercent = $headers['X-SavedPercent'];

Server Upgrade

May 3, 2014

Nathaniel Hyson

Downtime s1 Servers Upgrades No Comments

Server (s1) is scheduled to have another SSD hard drive added to it on:

5.4.2014 (Sun) 01:00 (GMT-0500) – 04:00 (GMT-0500)

Shouldn’t be any downtime as it’s simply a hard drive however there may be some downtime between 10pm PST and 1am PST.

Referral Credits

May 1, 2014

Nathaniel Hyson

Clients Offers & Specials No Comments

The below promotional offer expires 2014/08/01 at 12am PST.

As systems for the control panel are starting to come together. I’ve decided to offer some incentive options for referrals.

Option 1: 5% off your Monthly additional charges (bandwidth, disk space, backups, db space, email space, dedicated IP) for 1 node. As long as your referred customer keeps their subscription.

Option 2: 100$ credit to your account for every 12 months your referred customer pays for server service (If the referred customer pays for 12 months now and then in 12 months pays for another 12 months you’ll get 200$ in account credit).

Each customer referred allows one of the two options for referral credit.

Essentially if you refer 32 customers to CLDMV your hosting is free (assuming 1 node in use) as long as those 32 customers keep service.

Note: Account credit is only redeemable for services and invoices. It is not redeemable for cash/money.

What is a node you may ask. A node is specified as a single domain/application. IE say you run example.com and example.net, each is a single node on our servers. Thus you are running 2 nodes.

Database backup system bugs

April 25, 2014

Nathaniel Hyson

Bugs Servers No Comments

A bug was found in the database backup system. This has been resolved. The bug was an issue with the backup system not properly removing old backups when it came to the database backups. HTML backups were being removed correctly though.

As a result of more coding the database backup system now supports sending the backup file to the correct website which the database is used for. For those using multiple sites and/or multiple databases.

Crons are here

April 16, 2014

Nathaniel Hyson

Features Servers No Comments

While there is still no control panel yet. The system now supports schedules crons. These crons can be set at a min interval of 5 minutes and are easily modified. So once the control panel is in place it will be easy to implement it into the panel.

Currently I have already setup the crons manually that were needed for some clients. If you need any crons setup for now just send me an email.

Note: These crons have a low priority in order to keep the server running smoothly. (nice commanded)

PHP CLI added, crons to come soon

April 9, 2014

Nathaniel Hyson

Features Servers No Comments

PHP has been added to the shells. There was a bug with the mysql side of this that didn’t let PHP load the mysql extensions. Now that that is fixed PHP can properly be used through the command line for each user.

With this being fixed cron jobs will be the second thing on my list to implement into the control panel.

Heart bleed bug

April 9, 2014

Nathaniel Hyson

Security Servers No Comments

A friend just pointed me to this: http://www.theepochtimes.com/n3/609175-heart-bleed-bug-imperils-web-encryption-putting-passwords-credit-cards-at-risk/ which in turn turned me to this: http://heartbleed.com/

Basically OpenSSL for 2 years had a major flaw in it which allows hackers to obtain 64 kilobytes of data from the server where OpenSSL was installed and being used. I rushed onto the server and checked the OpenSSL for it’s version number. While I will not specifically state what version the servers are running for security measures I will say that the service is NOT running OpenSSL versions which were vulnerable.

However after using a test site (http://filippo.io/Heartbleed/) on a client’s server I found that even though 1.0.0 was not supoused to be affect (their version was 1.0.0c) they were vulnerable. I would strongly urge ANYONE to either run their update program (centos/rhel: “yum -y update openssl”) or manually install 1.0.1g as soon as possible. Then broadcast to your account holders to change their passwords.

Keep in mind OpenSSL 1.0.0c was released in December of 2010. Which means if 1.0.0c was vulnerable this bug has been around for 3 1/2 years.


openssl version
OpenSSL 1.0.0c 2 Dec 2010

openssl version

OpenSSL 1.0.0c 2 Dec 2010

Excerpt from http://heartbleed.com/

What versions of the OpenSSL are affected?

Status of different versions:

OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
OpenSSL 1.0.1g is NOT vulnerable
OpenSSL 1.0.0 branch is NOT vulnerable
OpenSSL 0.9.8 branch is NOT vulnerable

Bug was introduced to OpenSSL in December 2011 and has been out in the wild since OpenSSL release 1.0.1 on 14th of March 2012. OpenSSL 1.0.1g released on 7th of April 2014 fixes the bug.

Commands to update your own dedicated server:


cd ~
wget https://www.openssl.org/source/openssl-1.0.1g.tar.gz
tar -zxvf openssl-1.0.1g.tar.gz
rm -Rf openssl-1.0.1g.tar.gz
cd openssl-1.0.1g
./config
make
make install
cd ..
rm -Rf openssl-1.0.1g

cd ~

wget https://www.openssl.org/source/openssl-1.0.1g.tar.gz

tar -zxvf openssl-1.0.1g.tar.gz

rm -Rf openssl-1.0.1g.tar.gz

cd openssl-1.0.1g

./config

make

make install

cd ..

rm -Rf openssl-1.0.1g

Just in case the above command doesn’t clean up here is the clean up command:


cd ~
rm -Rf openssl-1.0.1g.tar.gz
rm -Rf openssl-1.0.1g

cd ~

rm -Rf openssl-1.0.1g.tar.gz

rm -Rf openssl-1.0.1g

In case you’re having issues with “openssl version” still showing you your old version and are using StorMan use the following commands:


mv /usr/StorMan/ssl/bin/openssl /usr/StorMan/ssl/bin/openssl-backup
ln -fs /usr/local/ssl/bin/openssl /usr/StorMan/ssl/bin/openssl

mv /usr/StorMan/ssl/bin/openssl /usr/StorMan/ssl/bin/openssl-backup

ln -fs /usr/local/ssl/bin/openssl /usr/StorMan/ssl/bin/openssl

If not using StorMan and still having issues of the old version being reported try:


mv /usr/bin/openssl /usr/bin/openssl-backup
ln -fs /usr/local/ssl/bin/openssl /usr/bin/openssl

mv /usr/bin/openssl /usr/bin/openssl-backup

ln -fs /usr/local/ssl/bin/openssl /usr/bin/openssl

To test your openssl version use the below command:


openssl version

openssl version

Also keep in mind you will want to re-key your SSL Certificates if your server had a known issue. As someone could be sitting on your private key just waiting to use it.