<?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>Atomic Secured Linux - Spheron1</title>
	<atom:link href="https://www.spheron1.uk/tag/atomic-secured-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.spheron1.uk</link>
	<description></description>
	<lastBuildDate>Mon, 27 Jun 2011 12:35:03 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>Parallels Plesk and Atomic Secured Linux</title>
		<link>https://www.spheron1.uk/2011/06/27/parallels-plesk-and-atomic-secured-linux/</link>
					<comments>https://www.spheron1.uk/2011/06/27/parallels-plesk-and-atomic-secured-linux/#comments</comments>
		
		<dc:creator><![CDATA[digitaldisaster]]></dc:creator>
		<pubDate>Mon, 27 Jun 2011 12:35:03 +0000</pubDate>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[ASL]]></category>
		<category><![CDATA[Atomic Secured Linux]]></category>
		<category><![CDATA[GRSecurity]]></category>
		<category><![CDATA[Parallels Plesk]]></category>
		<category><![CDATA[PSA]]></category>
		<guid isPermaLink="false">https://www.spheron1.uk/?p=449</guid>

					<description><![CDATA[<p>If you are experiencing HTTP 500 Internal Server Error messages from the license management part of the Parallels Plesk control panel when running on Atomic Secured Linux, then you are probably running into some buggy anti-reverse engineering code that Parallels have built into the Plesk software. It seems that Parallels are using ptrace to determine if someone has attached a&#46;&#46;&#46;</p>
<p>The post <a href="https://www.spheron1.uk/2011/06/27/parallels-plesk-and-atomic-secured-linux/">Parallels Plesk and Atomic Secured Linux</a> first appeared on <a href="https://www.spheron1.uk">Spheron1</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>If you are experiencing HTTP 500 Internal Server Error messages from the license management part of the Parallels Plesk control panel when running on Atomic Secured Linux, then you are probably running into some buggy anti-reverse engineering code that Parallels have built into the Plesk software.</p>
<p>It seems that Parallels are using ptrace to determine if someone has attached a debugger to Plesk in order to reverse engineer it. The problem is that AtomiCorp have implemented GRSecurity ptrace protection in the Atomic Secured Linux kernel in order to prevent malicious software such as TTY sniffers and Parallels Plesk is incorrectly interpreting it&#8217;s inability to ptrace as suspicious debugging behaviour.</p>
<p>Until Parallels fix this behaviour in Plesk (and there is no sign that they will, given that it has been a known issue for many months), then the only thing that you can to is disable the GRSecurity ptrace feature in the Atomic Secured Linux kernel. This can be done whilst the system is running using sysctl:</p>
<blockquote><p>sysctl -w kernel.grsecurity.harden_ptrace=0</p></blockquote>
<p>In order to make this change permanent so that it doesn&#8217;t disappear every time you reboot your server, you will need to edit /etc/sysctl.conf and add the following line:</p>
<blockquote><p>kernel.grsecurity.harden_ptrace = 0</p></blockquote>
<p>Now restart the Parallels Plesk service and enjoy your error free license management <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p><p>The post <a href="https://www.spheron1.uk/2011/06/27/parallels-plesk-and-atomic-secured-linux/">Parallels Plesk and Atomic Secured Linux</a> first appeared on <a href="https://www.spheron1.uk">Spheron1</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.spheron1.uk/2011/06/27/parallels-plesk-and-atomic-secured-linux/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>R1Soft CDP 3.0 with Atomic Secured Linux and PAX</title>
		<link>https://www.spheron1.uk/2011/06/12/r1soft-cdp-3-0-with-atomic-secured-linux-and-pax/</link>
					<comments>https://www.spheron1.uk/2011/06/12/r1soft-cdp-3-0-with-atomic-secured-linux-and-pax/#respond</comments>
		
		<dc:creator><![CDATA[digitaldisaster]]></dc:creator>
		<pubDate>Sun, 12 Jun 2011 10:41:10 +0000</pubDate>
				<category><![CDATA[R1Soft CDP]]></category>
		<category><![CDATA[ASL]]></category>
		<category><![CDATA[Atomic Secured Linux]]></category>
		<category><![CDATA[CDP]]></category>
		<category><![CDATA[CDP Advanced Edition]]></category>
		<category><![CDATA[CDP Enterprise Edition]]></category>
		<category><![CDATA[CDP Standard Edition]]></category>
		<category><![CDATA[CDP3]]></category>
		<category><![CDATA[CDP3.0]]></category>
		<category><![CDATA[PAX]]></category>
		<category><![CDATA[R1Soft]]></category>
		<guid isPermaLink="false">https://www.spheron1.uk/?p=412</guid>

					<description><![CDATA[<p>If you want to run R1Soft CDP 3.0 on a system protected by Atomic Secured Linux and the ASL enhanced kernel with PaX/grsecurity then you need to disable memory protection for the CDP 3.0 binary. You do this by using paxctl to set the NOMPROTECT flag for the CDP 3.0 binary. /sbin/paxctl -m /usr/sbin/r1soft/bin/2-6/cdp-2-6 Unfortunately the CDP 3.0 binary lacks&#46;&#46;&#46;</p>
<p>The post <a href="https://www.spheron1.uk/2011/06/12/r1soft-cdp-3-0-with-atomic-secured-linux-and-pax/">R1Soft CDP 3.0 with Atomic Secured Linux and PAX</a> first appeared on <a href="https://www.spheron1.uk">Spheron1</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>If you want to run R1Soft CDP 3.0 on a system protected by Atomic Secured Linux and the ASL enhanced kernel with PaX/grsecurity then you need to disable memory protection for the CDP 3.0 binary. You do this by using paxctl to set the NOMPROTECT flag for the CDP 3.0 binary. </p>
<blockquote><p>/sbin/paxctl -m /usr/sbin/r1soft/bin/2-6/cdp-2-6</p></blockquote>
<p>Unfortunately the CDP 3.0 binary lacks the PT_PAX_FLAGS header, so you will receive an error message along the lines of:</p>
<blockquote><p>file /usr/sbin/r1soft/bin/2-6/cdp-2-6 does not have a PT_PAX_FLAGS program header, try conversion</p></blockquote>
<p>The solution to this is to first use paxctl to run a conversion on the CDP 3.0 binary which should change the PT_GNU_STACK header to PT_PAX_FLAGS</p>
<blockquote><p>/sbin/paxctl -c /usr/sbin/r1soft/bin/2-6/cdp-2-6 </p></blockquote>
<p>If this has worked then you should see a message along the lines of </p>
<blockquote><p>file /usr/sbin/r1soft/bin/2-6/cdp-2-6 had a PT_GNU_STACK program header, converted</p></blockquote>
<p>Now you should be able to use paxctl to set the NOMPROTECT flag on the CDP 3.0 binary without any errors. Now restart the R1Soft CDP 3.0 agent service and have fun backing up all your previous data <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p><p>The post <a href="https://www.spheron1.uk/2011/06/12/r1soft-cdp-3-0-with-atomic-secured-linux-and-pax/">R1Soft CDP 3.0 with Atomic Secured Linux and PAX</a> first appeared on <a href="https://www.spheron1.uk">Spheron1</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.spheron1.uk/2011/06/12/r1soft-cdp-3-0-with-atomic-secured-linux-and-pax/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 0/76 objects using Redis
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Redis

Served from: spheron1.uk @ 2026-08-06 22:26:10 by W3 Total Cache
-->