<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: When is a crashing MySQL bug not a bug?</title>
	<atom:link href="http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/feed/" rel="self" type="application/rss+xml" />
	<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/</link>
	<description>Expert times and information on MySQL</description>
	<lastBuildDate>Thu, 09 May 2013 15:50:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Tech Crunch: Culture Clash &#38; Oracle Makes More Moves To Kill Open Source MySQL &#124; Timsiu&#039;s Blog</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-16418</link>
		<dc:creator>Tech Crunch: Culture Clash &#38; Oracle Makes More Moves To Kill Open Source MySQL &#124; Timsiu&#039;s Blog</dc:creator>
		<pubDate>Sun, 28 Oct 2012 10:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-16418</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressedhere and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressedhere and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shantanu Oak</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15896</link>
		<dc:creator>Shantanu Oak</dc:creator>
		<pubDate>Thu, 13 Sep 2012 12:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15896</guid>
		<description>... Because &quot;All people are equal but some are more equal than others!&quot;
Oracle is obviously trying to protect it&#039;s company interest and I do not see anything wrong in it. 
The community / customer will pay the price for non-transparency and the price is always fair once paid in full.</description>
		<content:encoded><![CDATA[<p>&#8230; Because &#8220;All people are equal but some are more equal than others!&#8221;<br />
Oracle is obviously trying to protect it&#8217;s company interest and I do not see anything wrong in it.<br />
The community / customer will pay the price for non-transparency and the price is always fair once paid in full.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: State of the MySQL forks &#124; OpenLife.cc</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15582</link>
		<dc:creator>State of the MySQL forks &#124; OpenLife.cc</dc:creator>
		<pubDate>Tue, 21 Aug 2012 13:35:20 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15582</guid>
		<description>[...] big news this week was the reports by Ronald Bradford (consultant), Sergei Golubchik (MariaDB) and Mark Callaghan (Facebook) that Oracle has yet again tightened the [...]</description>
		<content:encoded><![CDATA[<p>[...] big news this week was the reports by Ronald Bradford (consultant), Sergei Golubchik (MariaDB) and Mark Callaghan (Facebook) that Oracle has yet again tightened the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hank Eskin</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15581</link>
		<dc:creator>Hank Eskin</dc:creator>
		<pubDate>Tue, 21 Aug 2012 12:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15581</guid>
		<description>I filed the original bug 65740.  What concerns me is that I&#039;m not sure this qualifies as &quot;A crash caused by non admin users is considered a privilege escalation.&quot; since two independent conditions must be met before the crash happens:

1.  Some form of &quot;replicate-wild-ignore-table&quot; or &quot;replicate-ignore-table&quot; has to exist in the my.cnf file
2.  An update statement using @ variables (this statement my crashing slave: &quot;update test set rank=@rnk:=@rnk+1&quot;)

Only the update statement can be submitted by a non-admin user. Only an admin user can add the replicate-ignore statements to the my.cnf file in order to cause a crashing slave.  If there are no &quot;replicate-ignore&quot; statements in the my.cnf file, the update statements work as expected without crashing the slave.

So I don&#039;t see why this is a security hazard triggered by a non-admin user.

Finally, if the bug itself is replicated and marked as duplicates elsewhere in the MySQL bug database (and Percona&#039;s), then what exactly is being accomplished by marking the original bug as private?</description>
		<content:encoded><![CDATA[<p>I filed the original bug 65740.  What concerns me is that I&#8217;m not sure this qualifies as &#8220;A crash caused by non admin users is considered a privilege escalation.&#8221; since two independent conditions must be met before the crash happens:</p>
<p>1.  Some form of &#8220;replicate-wild-ignore-table&#8221; or &#8220;replicate-ignore-table&#8221; has to exist in the my.cnf file<br />
2.  An update statement using @ variables (this statement my crashing slave: &#8220;update test set rank=@rnk:=@rnk+1&#8243;)</p>
<p>Only the update statement can be submitted by a non-admin user. Only an admin user can add the replicate-ignore statements to the my.cnf file in order to cause a crashing slave.  If there are no &#8220;replicate-ignore&#8221; statements in the my.cnf file, the update statements work as expected without crashing the slave.</p>
<p>So I don&#8217;t see why this is a security hazard triggered by a non-admin user.</p>
<p>Finally, if the bug itself is replicated and marked as duplicates elsewhere in the MySQL bug database (and Percona&#8217;s), then what exactly is being accomplished by marking the original bug as private?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricardo Parente&#039;s Blog &#187; Oracle Makes More Moves To Kill Open Source MySQL</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15580</link>
		<dc:creator>Ricardo Parente&#039;s Blog &#187; Oracle Makes More Moves To Kill Open Source MySQL</dc:creator>
		<pubDate>Tue, 21 Aug 2012 12:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15580</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill MySQL &#124; KlineTel</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15578</link>
		<dc:creator>Oracle Makes More Moves To Kill MySQL &#124; KlineTel</dc:creator>
		<pubDate>Tue, 21 Aug 2012 07:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15578</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL via Techcrunch.com - Edno360</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15577</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL via Techcrunch.com - Edno360</dc:creator>
		<pubDate>Tue, 21 Aug 2012 05:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15577</guid>
		<description>[...] The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle、オープンソースのMySQL潰しに次の一手</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15574</link>
		<dc:creator>Oracle、オープンソースのMySQL潰しに次の一手</dc:creator>
		<pubDate>Tue, 21 Aug 2012 00:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15574</guid>
		<description>[...] OracleがMySQLの利用を可能な限り困難にしようとしていることは明白だ。その結果デベロッパー・コミュニティーでは、Oracelが何をオープンと考え何をクローズドと考えるかに関する不信の波が広がっている。デベロッパーに起きている問題は、ここやここに、さまざまな形で表現されている。 [...]</description>
		<content:encoded><![CDATA[<p>[...] OracleがMySQLの利用を可能な限り困難にしようとしていることは明白だ。その結果デベロッパー・コミュニティーでは、Oracelが何をオープンと考え何をクローズドと考えるかに関する不信の波が広がっている。デベロッパーに起きている問題は、ここやここに、さまざまな形で表現されている。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Verschleiert Oracle MySQL-Informationen? - Der Softwareentwickler Blog</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15571</link>
		<dc:creator>Verschleiert Oracle MySQL-Informationen? - Der Softwareentwickler Blog</dc:creator>
		<pubDate>Mon, 20 Aug 2012 19:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15571</guid>
		<description>[...] berichtet Ronald Bradford in seinem Blog von einem kritischen Fehler, der eine komplette MySQL-Datenbank zum Crashen [...]</description>
		<content:encoded><![CDATA[<p>[...] berichtet Ronald Bradford in seinem Blog von einem kritischen Fehler, der eine komplette MySQL-Datenbank zum Crashen [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linux, BSD un citas lietas - Atvērtajās ziņās &#124; MySQL pamazām zaudē atvērtību?</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15567</link>
		<dc:creator>Linux, BSD un citas lietas - Atvērtajās ziņās &#124; MySQL pamazām zaudē atvērtību?</dc:creator>
		<pubDate>Mon, 20 Aug 2012 14:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15567</guid>
		<description>[...] un citu ar MySQL saistīto projektu dalībnieki izteikuši bažas par to, ka ir pārtraukta svarīgu komponentu koda publiskošana. MySQL pakāpeniski pārvēršas [...]</description>
		<content:encoded><![CDATA[<p>[...] un citu ar MySQL saistīto projektu dalībnieki izteikuši bažas par to, ka ir pārtraukta svarīgu komponentu koda publiskošana. MySQL pakāpeniski pārvēršas [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15559</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL</dc:creator>
		<pubDate>Mon, 20 Aug 2012 06:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15559</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed hereand here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed hereand here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL - The Review Blog</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15555</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL - The Review Blog</dc:creator>
		<pubDate>Sun, 19 Aug 2012 23:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15555</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL теряет былую открытость &#8212; прекращена публикация тестовых наборов и лога изменений : Записки начинающего линуксоида</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15551</link>
		<dc:creator>MySQL теряет былую открытость &#8212; прекращена публикация тестовых наборов и лога изменений : Записки начинающего линуксоида</dc:creator>
		<pubDate>Sun, 19 Aug 2012 20:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15551</guid>
		<description>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</description>
		<content:encoded><![CDATA[<p>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress Themes &#187; Blog Archive &#187; Oracle Makes More Moves To Kill Open Source MySQL</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15537</link>
		<dc:creator>Wordpress Themes &#187; Blog Archive &#187; Oracle Makes More Moves To Kill Open Source MySQL</dc:creator>
		<pubDate>Sun, 19 Aug 2012 09:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15537</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL -&#62; TheirSQL? &#124; Lindeas</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15535</link>
		<dc:creator>MySQL -&#62; TheirSQL? &#124; Lindeas</dc:creator>
		<pubDate>Sun, 19 Aug 2012 08:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15535</guid>
		<description>[...] на списъка с промените и на тестовите скриптове. Така не се разбира какви грешки всъщност са отстранени в тази версия и никой външен [...]</description>
		<content:encoded><![CDATA[<p>[...] на списъка с промените и на тестовите скриптове. Така не се разбира какви грешки всъщност са отстранени в тази версия и никой външен [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL теряет былую открытость &#8212; прекращена публикация тестовых наборов и лога изменений &#124; Интересное в сети</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15530</link>
		<dc:creator>MySQL теряет былую открытость &#8212; прекращена публикация тестовых наборов и лога изменений &#124; Интересное в сети</dc:creator>
		<pubDate>Sun, 19 Aug 2012 06:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15530</guid>
		<description>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</description>
		<content:encoded><![CDATA[<p>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Startup Help</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15528</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Startup Help</dc:creator>
		<pubDate>Sun, 19 Aug 2012 04:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15528</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Hosting In</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15524</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Hosting In</dc:creator>
		<pubDate>Sun, 19 Aug 2012 03:32:52 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15524</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL - VitalIT &#124; VitalIT</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15523</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL - VitalIT &#124; VitalIT</dc:creator>
		<pubDate>Sun, 19 Aug 2012 03:20:05 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15523</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; AkimoLux.com</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15522</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; AkimoLux.com</dc:creator>
		<pubDate>Sun, 19 Aug 2012 03:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15522</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Crowdfunding News</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15518</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Crowdfunding News</dc:creator>
		<pubDate>Sun, 19 Aug 2012 02:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15518</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Krantenkoppen Tech</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15517</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Krantenkoppen Tech</dc:creator>
		<pubDate>Sun, 19 Aug 2012 02:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15517</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; E-7</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15514</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; E-7</dc:creator>
		<pubDate>Sun, 19 Aug 2012 01:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15514</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Gaster Tech Blog</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15513</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Gaster Tech Blog</dc:creator>
		<pubDate>Sun, 19 Aug 2012 01:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15513</guid>
		<description>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It’s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; Welcome To My Site</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15508</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; Welcome To My Site</dc:creator>
		<pubDate>Sun, 19 Aug 2012 00:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15508</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oracle Makes More Moves To Kill Open Source MySQL &#124; TechCrunch</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15504</link>
		<dc:creator>Oracle Makes More Moves To Kill Open Source MySQL &#124; TechCrunch</dc:creator>
		<pubDate>Sat, 18 Aug 2012 23:38:51 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15504</guid>
		<description>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s pretty clear that Oracle is trying to make it as difficult as possible to use MySQL. The result is a wave of unsettlement in the developer community about what Oracle considers open and what it sees as closed. The move is causing problems for developers in all manner of ways as expressed here and here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL теряет былую открытость&#160;&#124;&#160;AllUNIX.ru &#8212; Всероссийский портал о UNIX-системах</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15500</link>
		<dc:creator>MySQL теряет былую открытость&#160;&#124;&#160;AllUNIX.ru &#8212; Всероссийский портал о UNIX-системах</dc:creator>
		<pubDate>Sat, 18 Aug 2012 15:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15500</guid>
		<description>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</description>
		<content:encoded><![CDATA[<p>[...] MariaDB и других связанных с MySQL проектов выразили опасение в связи с прекращением публикации некоторых важных [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Christophe Petit</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15499</link>
		<dc:creator>Jean-Christophe Petit</dc:creator>
		<pubDate>Sat, 18 Aug 2012 15:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15499</guid>
		<description>Hello Ronald,

we also open a bug #65831 (http://bugs.mysql.com/bug.php?id=65831) and it was mentioned as a duplicate of yours by Valeriy Kravchuk. And then it was crossed out..
When we tried to look at your bug, the only message displayed was &quot;You do not have access to bug #65740&quot; (bug was mark as private)
Thank to Google cache, we were able to look into it and it looks in fact very similar to yours..
Why did your bug was marked as private but not ours ?
When we looked into the changes of 5.5.27, there is no mention of either your bug or ours ??
We also never received a notification that our bug was fixed, or was it ? Message from Hank Eskin is not clear as he mentioned your bug number but crossed out..
Note: an other similar bug listed in Percona (https://bugs.launchpad.net/percona-server/+bug/1028356) was referred as a duplicate.</description>
		<content:encoded><![CDATA[<p>Hello Ronald,</p>
<p>we also open a bug #65831 (<a href="http://bugs.mysql.com/bug.php?id=65831" rel="nofollow">http://bugs.mysql.com/bug.php?id=65831</a>) and it was mentioned as a duplicate of yours by Valeriy Kravchuk. And then it was crossed out..<br />
When we tried to look at your bug, the only message displayed was &#8220;You do not have access to bug #65740&#8243; (bug was mark as private)<br />
Thank to Google cache, we were able to look into it and it looks in fact very similar to yours..<br />
Why did your bug was marked as private but not ours ?<br />
When we looked into the changes of 5.5.27, there is no mention of either your bug or ours ??<br />
We also never received a notification that our bug was fixed, or was it ? Message from Hank Eskin is not clear as he mentioned your bug number but crossed out..<br />
Note: an other similar bug listed in Percona (<a href="https://bugs.launchpad.net/percona-server/+bug/1028356" rel="nofollow">https://bugs.launchpad.net/percona-server/+bug/1028356</a>) was referred as a duplicate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint Byrum</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15494</link>
		<dc:creator>Clint Byrum</dc:creator>
		<pubDate>Sat, 18 Aug 2012 06:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15494</guid>
		<description>Back when I was pushing hard for answers on Oracle&#039;s non-disclosure policies this was explained to me. Basically mysql engineers have their hands tied by the policy if it is deemed a security problem. A crash caused by non admin users is considered a privilege escalation. So, we will not be seeing test cases (since they are taylor made exploit scripts) nor will these bugs be made public again. :-[ I suspect they the desire not to disclose info about security bugs may also be delaying the bzr tree updates as well.</description>
		<content:encoded><![CDATA[<p>Back when I was pushing hard for answers on Oracle&#8217;s non-disclosure policies this was explained to me. Basically mysql engineers have their hands tied by the policy if it is deemed a security problem. A crash caused by non admin users is considered a privilege escalation. So, we will not be seeing test cases (since they are taylor made exploit scripts) nor will these bugs be made public again. :-[ I suspect they the desire not to disclose info about security bugs may also be delaying the bzr tree updates as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-08-15/comment-page-1/#comment-15483</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Fri, 17 Aug 2012 09:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=4100#comment-15483</guid>
		<description>If the crash is something that can be triggered by a non-admin user, it&#039;s likely to be treated as security by Oracle now, and any public info on it heavily obfuscated.  It may re-surface months later via a Critical Patch Update in form of a CVE with no details allowing mapping it to an actual flaw.  Though, you may ask in bug if it&#039;s treated as security and request information about what CVE is / will be assigned to it and make it public to help those who won&#039;t get it if they ask.

http://www.attrition.org/pipermail/vim/2012-June/002562.html

The above is likely to provide an explanation to the Sergei&#039;s query, as an attempt to avoid similar:

http://www.h-online.com/security/news/item/Oracle-accidentally-release-MySQL-DoS-proof-of-concept-1526146.html</description>
		<content:encoded><![CDATA[<p>If the crash is something that can be triggered by a non-admin user, it&#8217;s likely to be treated as security by Oracle now, and any public info on it heavily obfuscated.  It may re-surface months later via a Critical Patch Update in form of a CVE with no details allowing mapping it to an actual flaw.  Though, you may ask in bug if it&#8217;s treated as security and request information about what CVE is / will be assigned to it and make it public to help those who won&#8217;t get it if they ask.</p>
<p><a href="http://www.attrition.org/pipermail/vim/2012-June/002562.html" rel="nofollow">http://www.attrition.org/pipermail/vim/2012-June/002562.html</a></p>
<p>The above is likely to provide an explanation to the Sergei&#8217;s query, as an attempt to avoid similar:</p>
<p><a href="http://www.h-online.com/security/news/item/Oracle-accidentally-release-MySQL-DoS-proof-of-concept-1526146.html" rel="nofollow">http://www.h-online.com/security/news/item/Oracle-accidentally-release-MySQL-DoS-proof-of-concept-1526146.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
