<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Protection &#8211; Hostry Help Center</title>
	<atom:link href="https://help.hostry.com/article-tags/protection/feed/" rel="self" type="application/rss+xml" />
	<link>https://help.hostry.com</link>
	<description>Full information on how to use HOSTRY, provided by 24/7 community based support</description>
	<lastBuildDate>Thu, 03 Dec 2020 10:24:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.9.12</generator>

<image>
	<url>https://help.hostry.com/wp-content/uploads/cache/2021/01/cropped-apple-icon-180x180-1/836712163.png</url>
	<title>Protection &#8211; Hostry Help Center</title>
	<link>https://help.hostry.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Free site protection with Let&#8217;s Encrypt</title>
		<link>https://help.hostry.com/knowledge-base/free-site-protection-with-lets-encrypt/</link>
					<comments>https://help.hostry.com/knowledge-base/free-site-protection-with-lets-encrypt/#respond</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 11 Jul 2019 12:12:53 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=202</guid>

					<description><![CDATA[Protection takes a very important role in the development of sites. People have experience of being exposed to external threats from intruders who are ready to steal personal data, important information and other resources from your site. Content, business, customers are all important factors, but the protection of the site [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image"><img width="645" height="413" src="https://help.hostry.com/wp-content/uploads/2019/07/sssss.png" alt="" class="wp-image-206" srcset="https://help.hostry.com/wp-content/uploads/2019/07/sssss.png 645w, https://help.hostry.com/wp-content/uploads/2019/07/sssss-300x192.png 300w, https://help.hostry.com/wp-content/uploads/2019/07/sssss-50x32.png 50w, https://help.hostry.com/wp-content/uploads/2019/07/sssss-600x384.png 600w, https://help.hostry.com/wp-content/uploads/2019/07/sssss-320x205.png 320w" sizes="(max-width: 645px) 100vw, 645px" /></figure>



<p></p>



<p>Protection takes a very important role in the development of sites. People have experience of being exposed to external threats from intruders who are ready to steal personal data, important information and other resources from your site. Content, business, customers are all important factors, but the protection of the site is above all the confidence in security and integrity.</p>



<p>An <strong>SSL certificate</strong> is a special protocol that guarantees a secure and reliable connection to your site. <strong><em>This protocol</em></strong> provides reliability, security, and is guaranteed a successful and non-dangerous communication through the elements of authentication and encryption. This fact adds your site status with the suffix &#8220;S&#8221; (that is, no longer http, but httpS)</p>



<p></p>



<h2 id="order-free-certificate-lets-encrypt" >Order free certificate Let&#8217;s Encrypt</h2>



<p>Let’s Encrypt ”is a certificate authority from which you can get a free SSL certificate for the site. They are great for small sites where users can leave some personal information: email, passwords, phone number, address. Certificate Authority Let&#8217;s Encrypt is ready to issue you a certificate absolutely FREE! </p>



<p>When installing a security certificate on any control panel, when ordering a certificate, you receive the following files:</p>



<ul><li><strong>certificate.crt</strong> – the basis of the certificate for your domain name.</li><li><strong>private.key</strong> – the key that was generated when creating the CSR</li><li><strong>ca_bundle.crt</strong> – root certificate provided by your certificate authority</li></ul>



<p>This is very useful for you if you own a small website and cannot afford a paid SSL certificate. We give you a free Let Encrypt security certificate for 90 days. Install the free version of Let Encrypt by clicking on the link: </p>



<p></p>



<p><a href="https://hostry.com/solutions/ssl-for-free/">https://hostry.com/solutions/ssl-for-free/</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/free-site-protection-with-lets-encrypt/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How To Protect NGINX web server from Logjam atack on CentOS</title>
		<link>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/</link>
					<comments>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/#comments</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 22 Aug 2019 11:01:21 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=567</guid>

					<description><![CDATA[When using a security certificate, many are confident in 100% protection of their web server, but we want to tell that there is a vulnerability in the security certificate. It cannot be called an ordinary vulnerability; rather, it is a small hole in the protocol itself during depreciation of SSL3 [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>When using a security certificate, many are confident in 100% protection of their web server, but we want to tell that there is a vulnerability in the security certificate. It cannot be called an ordinary vulnerability; rather, it is a small hole in the protocol itself during depreciation of SSL3 and a phased transition to the use of SSL2.</p>



<p>Today there are many web services that are vulnerable to this Logiam attack. We will try to understand how it can be done to secure your server. We will be talking about servers with the operating system CentOS, version 6 and 7.</p>



<h2 id="specific-actions" >Specific actions </h2>



<p>First, check to see if your server is actually vulnerable by checking Qualys SSL. If your server is vulnerable, there will be a message at the top of the page. After you confirm that the server is vulnerable, enter the NGINX installation directory</p>



<pre class="wp-block-code"><code>cd /etc/nginx/
mkdir keygroup
cd keygroup</code></pre>



<p>Next, you need to run the following command to create a key group</p>



<pre class="wp-block-code"><code>openssl dhparam -out dhsecure.pem 2048</code></pre>



<p>The next step is to add a new key group to your NGINX configuration</p>



<pre class="wp-block-code"><code>cd /etc/nginx/
vi .conf</code></pre>



<p>Next, add<strong><code> ssl_dhparam ... </code></strong>a line of code that is visible below inside each SSL server block and then update all server blocks. Update all blocks of your SSL server accordingly</p>



<pre class="wp-block-code"><code>server {
listen 443 ssl;
...
location / {
...
ssl_dhparam /etc/nginx/keygroup/dhsecure.pem
...
}</code></pre>



<p>Then a reboot of the NGINX web server should follow</p>



<pre class="wp-block-code"><code>service nginx reload</code></pre>



<p>Finally, test the server again with SSL certificate verification</p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/feed/</wfw:commentRss>
			<slash:comments>460</slash:comments>
		
		
			</item>
		<item>
		<title>How To Protect Your Server</title>
		<link>https://help.hostry.com/knowledge-base/how-to-protect-your-server/</link>
					<comments>https://help.hostry.com/knowledge-base/how-to-protect-your-server/#comments</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Tue, 16 Jul 2019 12:56:21 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=293</guid>

					<description><![CDATA[The topic of security has always been relevant in the IT industry. In this article we will give some tips on how to secure your server and try to help to ensure that your server is not subjected to threats and attacks. If you found approximately such a message during [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image"><img loading="lazy" width="729" height="518" src="https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22.png" alt="" class="wp-image-302" srcset="https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22.png 729w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22-300x213.png 300w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22-50x36.png 50w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22-600x426.png 600w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-16-14-54-22-320x227.png 320w" sizes="(max-width: 729px) 100vw, 729px" /></figure>



<p>The topic of security has always been relevant in the IT industry. In this article we will give some tips on how to secure your server and try to help to ensure that your server is not subjected to threats and attacks.</p>



<pre class="wp-block-code"><code>Last failed login: Mon Apr 15 13:52:45 MSK 2017 from 1.1.1.1 on ssh:notty
There were 4395 failed login attempts since the last successful login.</code></pre>



<p>If you found approximately such a message during your authorization to the server, it means that unsuccessful authorization attempts were made by someone else. Malicious users pick up SSH passwords purposefully (automatically, or using programmed infected computers).</p>



<h2 id="configure-authorization-from-specific-ip" >Configure authorization from specific IP</h2>



<p>Configure authorization from specific IP If you plan to connect to the server and conduct work only strictly from one device and / or only from certain IP addresses, you can enter the following lines: </p>



<pre class="wp-block-code"><code>/etc/hosts.deny
sshd: ALL</code></pre>



<p>In this file: </p>



<pre class="wp-block-preformatted"><strong>/etc/hosts.allow
Sshd: Your IP address</strong></pre>



<p>Thus, SSH access for all subnets except the specified one will be denied. After that, you need to restart the service using the service:</p>



<p></p>



<p><code><strong>service sshd restart</strong></code></p>



<p></p>



<h2 id="change-ssh-port" >Change SSH port</h2>



<p>To change the SSH port you need to uncomment this file <code><strong>/etc/ssh/sshd_config</strong></code>&nbsp;and change Port 22 to a free one, it can be any number up to 65536</p>



<p>After that, you need to start the server with the command:</p>



<p><code><strong>service sshd restart</strong></code></p>



<p></p>



<h2 id="use-ssh-keys" >Use SSH keys</h2>



<p></p>



<p>The advantage and advantage of this method is that you can be authorized on the server without regularly having to send your password through the network. </p>



<p>Even if someone listens on your connection, he will not have the opportunity to intercept and crack your password, since in fact it is never transmitted. Also, using SSH to identify keys eliminates the risk associated with brute-force attacks, by significantly reducing the attacker&#8217;s chance to guess the correct credentials. <br>The key pair is created using the command</p>



<pre class="wp-block-preformatted"><strong>ssh-keygen</strong></pre>



<p>The private key (file without extension) is copied to the PC, and the public key (keyname.pub) is copied to the file on the server. <code><strong>.ssh / authorized_keys</strong></code><strong>  </strong></p>



<p>In order to disable password authorization, in the same SSH configuration, you need to change the <strong><code>PasswordAuthentication yes directive to PasswordAuthentication no</code></strong> and restart the service &#8211; authorization will remain only with the SSH key.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/how-to-protect-your-server/feed/</wfw:commentRss>
			<slash:comments>453</slash:comments>
		
		
			</item>
	</channel>
</rss>
