<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=1761&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Jessie & Huge Dirty Cow]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=1761</link>
		<description><![CDATA[The most recent posts in Jessie & Huge Dirty Cow.]]></description>
		<lastBuildDate>Wed, 06 Dec 2017 14:41:28 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Jessie & Huge Dirty Cow]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=6576#p6576</link>
			<description><![CDATA[<p>Your link shows that so far, it&#039;s only fixed in sid. That means it&#039;s also fixed in ceres. It&#039;s only been about a week, so I guess the fix will be moving down to testing and stable soon. Whenever that happens in debian, it will happen in devuan a minute or two later. I hope they fix it in oldstable, too.</p><div class="codebox"><pre><code>aptitude -t sid search linux-image-4.14
p   linux-image-4.14.0-1-amd64                           - Linux 4.14 for 64-bit PCs

aptitude show linux-image-4.14.0-1-amd64
Package: linux-image-4.14.0-1-amd64      
New: yes
State: not installed
Version: 4.14.2-1

apt-cache policy linux-image-4.14.0-1-amd64
linux-image-4.14.0-1-amd64:
  Installed: (none)
  Candidate: 4.14.2-1
  Version table:
     4.14.2-1 0
        100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
         10 http://debian.csail.mit.edu/debian/ sid/main amd64 Packages</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Wed, 06 Dec 2017 14:41:28 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=6576#p6576</guid>
		</item>
		<item>
			<title><![CDATA[Re: Jessie & Huge Dirty Cow]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=6575#p6575</link>
			<description><![CDATA[<p>No, that was Dirty Cow, and the fix contained a vulnerability in case Transparent Huge Pages were enabled, therefore the &quot;Huge Dirty Cow&quot;.</p><p><a href="https://security-tracker.debian.org/tracker/CVE-2017-1000405/" rel="nofollow">https://security-tracker.debian.org/tra … 7-1000405/</a></p>]]></description>
			<author><![CDATA[dummy@example.com (ghp)]]></author>
			<pubDate>Wed, 06 Dec 2017 13:43:56 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=6575#p6575</guid>
		</item>
		<item>
			<title><![CDATA[Re: Jessie & Huge Dirty Cow]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=6559#p6559</link>
			<description><![CDATA[<p>Wasn&#039;t that fixed a year ago?<br /><a href="https://security-tracker.debian.org/tracker/CVE-2016-5195" rel="nofollow">https://security-tracker.debian.org/tra … -2016-5195</a></p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Tue, 05 Dec 2017 13:17:39 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=6559#p6559</guid>
		</item>
		<item>
			<title><![CDATA[Jessie & Huge Dirty Cow]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=6558#p6558</link>
			<description><![CDATA[<p>Is Jessie&#039;s kernel vulnerable for Huge Dirty Cow?</p><p>It looks as if we&#039;re not using Transparent Huge Pages.</p><p># cat /proc/meminfo | grep -i huge</p><p>returns nothing.</p><p>But, in case I&#039;m mistaken: <a href="https://github.com/torvalds/linux/commit/a8f97366452ed491d13cf1e44241bc0b5740b1f0" rel="nofollow">https://github.com/torvalds/linux/commi … 0b5740b1f0</a></p><p>Kind regards,</p><p>Gerard</p>]]></description>
			<author><![CDATA[dummy@example.com (ghp)]]></author>
			<pubDate>Tue, 05 Dec 2017 11:37:15 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=6558#p6558</guid>
		</item>
	</channel>
</rss>
