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: <1159528068.13029.12.camel@localhost.localdomain>
Date:	Fri, 29 Sep 2006 12:07:47 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Helge Hafting <helge.hafting@...el.hist.no>
Cc:	tglx@...utronix.de, Neil Brown <neilb@...e.de>,
	Michiel de Boer <x@...elhomicide.demon.nl>,
	James Bottomley <James.Bottomley@...elEye.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

Ar Gwe, 2006-09-29 am 12:15 +0200, ysgrifennodd Helge Hafting:
> This seems silly to me.  Sure, lasers and medical equipment is
> dangerous if used wrong.  When such equipment is
> controlled by software, then changing that software brings
> huge responsibility.  But it shouldn't be made impossible.

You will note that large corporations like telcos routinely push for
such legislation and rules to increase the burdens on smaller companies
and prevent competition. 

> > - Regulations to prevent unauthorized access to radio frequencies, which
> > is what concerns e.g. cellphone manufacturers.
> >   
> Unauthorized use is illegal and easy enough to track down.
> No special protection is needed.  And it cannot be enforced
> by making the phones har to modify - any radio amateur knows

Indeed - the regulations exist so that the state can control who makes
phones, ensure they contain the GSM crypto backdoors and don't support
additional voice scrambling or call relay type onion routing etc.

Alan
-
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/