linux-kernel - Re: GPLv3 Position Statement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0609271336200.3952@g5.osdl.org>
Date:	Wed, 27 Sep 2006 13:41:48 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Krzysztof Halasa <khc@...waw.pl>
cc:	Nicolas Mailhot <nicolas.mailhot@...oste.net>,
	linux-kernel@...r.kernel.org,
	James Bottomley <James.Bottomley@...elEye.com>
Subject: Re: GPLv3 Position Statement

On Wed, 27 Sep 2006, Krzysztof Halasa wrote:
> > And it not at all uncommon to have a flash that simply cannot be upgraded 
> > without opening the box. Even a lot of PC's have that: a lot (most?) PC's 
> > have a flash that has a separate _hardware_ pin that says that it is 
> > (possibly just partially) read-only. So in order to upgrade it, you'd 
> > literally need to open the case up, set a jumper, and _then_ run the 
> > program to reflash it.
> 
> I think this is history. Yes, late 486s and Pentiums (60 and 66?)
> had a jumper protecting the flash. It's not true since ca. "Pentium 75+"
> days - while many boards use "bootblock" chips, it's (almost?) always
> unprotected (at most it just requires setting some GPIO pin(s)). The
> rest of flash obviously has to be R/W to support the ESCD etc.

You're probably right. The pin still exists on the flash chips, but most 
of the time on PC's at least the writability is software-controlled.

I think the hatred of pins became so high that it became almost 
unacceptable for motherboard designers to add them on PC's. Nobody wants 
to open their case any more ;)

But the whole point was to just show how silly the whole "upgradable" vs 
"not upgradable" discussion is. We're literally talking about something 
where apparently it matters to the GPLv3 whether a pin on a chip is 
connected to software or hardware (or not at all). Is that sane?

So if it's "hardware-controlled", it would be ok (because it's not meant 
to be upgraded at all)? But if it's software-controlled it is not? A set 
of rules that require this kind of nitpicking is just broken.

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/