<?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: Linux under GPL version 3?</title>
	<atom:link href="http://www.p2pnet.net/story/7867/feed" rel="self" type="application/rss+xml" />
	<link>http://www.p2pnet.net/story/7867</link>
	<description>p2pnet.net - reader powered</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:11:09 -0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/7867/comment-page-1#comment-33957</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 10 Feb 2006 21:37:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-33957</guid>
		<description>&quot;I can only speculate as to the reasoning behind such a move, but I&#039;m sure that it has to do with preventing the use of drivers which do not enforce Windows DRM.&quot;

sure and you get to charge the hardware vendors for certifying their hardware.....You didn&#039;t think it was just about getting the media cartels money did you? No it&#039;s about getting more money from the customer through the hardware venders and the media cartels.


</description>
		<content:encoded><![CDATA[<p>&#8220;I can only speculate as to the reasoning behind such a move, but I&#8217;m sure that it has to do with preventing the use of drivers which do not enforce Windows DRM.&#8221;</p>
<p>sure and you get to charge the hardware vendors for certifying their hardware&#8230;..You didn&#8217;t think it was just about getting the media cartels money did you? No it&#8217;s about getting more money from the customer through the hardware venders and the media cartels.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/7867/comment-page-1#comment-33936</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 10 Feb 2006 16:02:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-33936</guid>
		<description>This didn&#039;t particularly belong in the last post, but I thought it was important to mention:

&gt; In fact there are rumors that Windows Vista will refuse to allow the 
&gt; use of unsigned drivers.

If Windows Vista does refuse to allow the use of unsigned drivers;  That would mean that you can&#039;t run the beta drivers from your favorite graphics card company that haven&#039;t been WHQL certified and signed yet, or even drivers like btwincap (http://btwincap.sourceforge.net/) the open source Brooktree based capture card drivers that are far superior to the ones supplied by the manufacturers of such cards.

I can only speculate as to the reasoning behind such a move, but I&#039;m sure that it has to do with preventing the use of drivers which do not enforce Windows DRM.</description>
		<content:encoded><![CDATA[<p>This didn&#8217;t particularly belong in the last post, but I thought it was important to mention:</p>
<p>&gt; In fact there are rumors that Windows Vista will refuse to allow the<br />
&gt; use of unsigned drivers.</p>
<p>If Windows Vista does refuse to allow the use of unsigned drivers;  That would mean that you can&#8217;t run the beta drivers from your favorite graphics card company that haven&#8217;t been WHQL certified and signed yet, or even drivers like btwincap (<a href="http://btwincap.sourceforge.net/" rel="nofollow">http://btwincap.sourceforge.net/</a>) the open source Brooktree based capture card drivers that are far superior to the ones supplied by the manufacturers of such cards.</p>
<p>I can only speculate as to the reasoning behind such a move, but I&#8217;m sure that it has to do with preventing the use of drivers which do not enforce Windows DRM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/7867/comment-page-1#comment-33935</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 10 Feb 2006 15:52:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-33935</guid>
		<description>&gt; I&#039;m not sure what the meaning of the &quot;digitally signed binaries&quot; is 
&gt; used for, but it appears that it doesn&#039;t refer to the private keys of 
&gt; someone like Linus but rather the DRM in the operating system or 
&gt; the source code.

It means that if you distribute GPL 3 code in a situation where the compiled code is some how verified, for example by checksum or cryptographic digital signature, you must provide a means for the person who is using the code to replace it and retain all original functionality.

A real life situation could be a stand alone device, such as a cellular phone, which verifies a cryptographic signature of the kernel binary or any other GPL software running on the device (such as libraries or applications), and then refuses to function or runs with reduced functionality if that verification fails.  In that case, it would be necessary to provide the private signing keys used to sign the binary in order to comply with GPL v3, but not version 2.

That problem could easily be solved by using a standard checksum which could be changed by the modifier, thus allowing modification of the software running on the device.  I don&#039;t know whether it would be acceptable for the device to simply present a warning that it is running unsigned code but not reduce any actual functionality, much the way that Windows XP now does.  That would be the method I would prefer.  That way I am notified that something has been changed, and can take appropriate action if I was not expecting the change.  Although, I&#039;m afraid, it would be much to tempting for manufacturers to reduce functionality in that situation.  In fact there are rumors that Windows Vista will refuse to allow the use of unsigned drivers.

Of course, the issue here is that preventing modification of the code is the goal that most manufacturers of stand alone equipment running GPL software are trying to prevent.  The problem with this is that most people agree that while it strictly adheres to the conditions in GPL v2, it does not follow the spirit of the license.

According to the article: Linus believes that it is alright to prevent people from running modified GPL software in certain situations.  While Richard Stallman (RMS) believes that if it is GPL, you should have the right to not only change it, but also to run it in the same context as the original version.  I happen to agree with RMS on this one.</description>
		<content:encoded><![CDATA[<p>&gt; I&#8217;m not sure what the meaning of the &#8220;digitally signed binaries&#8221; is<br />
&gt; used for, but it appears that it doesn&#8217;t refer to the private keys of<br />
&gt; someone like Linus but rather the DRM in the operating system or<br />
&gt; the source code.</p>
<p>It means that if you distribute GPL 3 code in a situation where the compiled code is some how verified, for example by checksum or cryptographic digital signature, you must provide a means for the person who is using the code to replace it and retain all original functionality.</p>
<p>A real life situation could be a stand alone device, such as a cellular phone, which verifies a cryptographic signature of the kernel binary or any other GPL software running on the device (such as libraries or applications), and then refuses to function or runs with reduced functionality if that verification fails.  In that case, it would be necessary to provide the private signing keys used to sign the binary in order to comply with GPL v3, but not version 2.</p>
<p>That problem could easily be solved by using a standard checksum which could be changed by the modifier, thus allowing modification of the software running on the device.  I don&#8217;t know whether it would be acceptable for the device to simply present a warning that it is running unsigned code but not reduce any actual functionality, much the way that Windows XP now does.  That would be the method I would prefer.  That way I am notified that something has been changed, and can take appropriate action if I was not expecting the change.  Although, I&#8217;m afraid, it would be much to tempting for manufacturers to reduce functionality in that situation.  In fact there are rumors that Windows Vista will refuse to allow the use of unsigned drivers.</p>
<p>Of course, the issue here is that preventing modification of the code is the goal that most manufacturers of stand alone equipment running GPL software are trying to prevent.  The problem with this is that most people agree that while it strictly adheres to the conditions in GPL v2, it does not follow the spirit of the license.</p>
<p>According to the article: Linus believes that it is alright to prevent people from running modified GPL software in certain situations.  While Richard Stallman (RMS) believes that if it is GPL, you should have the right to not only change it, but also to run it in the same context as the original version.  I happen to agree with RMS on this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/7867/comment-page-1#comment-33886</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 10 Feb 2006 02:56:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-33886</guid>
		<description>I&#039;m not sure what the meaning of the &quot;digitally signed binaries&quot; is used for, but it appears that it doesn&#039;t refer to the private keys of someone like Linus but rather the DRM in the operating system or the source code.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure what the meaning of the &#8220;digitally signed binaries&#8221; is used for, but it appears that it doesn&#8217;t refer to the private keys of someone like Linus but rather the DRM in the operating system or the source code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


