linux-kernel - Re: [ANNOUNCE] Position Statement on Linux Kernel Modules

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: <20080624113347.GA5246@hp0.dynamicro.ca>
Date:	Tue, 24 Jun 2008 07:33:47 -0400
From:	Greg Louis <glouis@...amicro.ca>
To:	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Position Statement on Linux Kernel Modules

Willy Tarreau wrote:

> > (Of course, the best way to rebut that argument [ that outside the
> > developer community, nobody cares whether drivers are proprietary ]
> > would be for end-users to vote with their feet, but for a lot of
> > us, me included, that's not a practical option.)
> 
> The problem is exactly what you describe in your last sentence. Hardware
> manufacturers are well aware of that and make no effort to provide correct
> drivers when they (think they) have a monopoly in certain areas.
> 
> What would be needed would be a public list of alternative hardware for
> known existing hardware.
...
> Willy

That is Utopian, I fear.  For example, what notebook supports the
installation of alternative hardware?  Go to another notebook, you
suggest?  Easy said: when I was buying the machine on which this is
being written, the choice of notebooks with 1920x1200 displays (a sine
qua non as far as I was concerned) was _extremely_ limited.  (There
actually was an open-source driver for the video of the one I picked,
but I could never get it to work.)  Similar difficulties exist for a
lot of special-purpose hardware; viable alternatives are rare.  Your
proposed list could certainly help ferret out such rarities, but I
doubt that it would suffice to make the problem go away.  I suspect,
too, that it would be a beast to maintain, given the need to track all
the features of all the versions of all the hardware items that were
listed.

Then again, my proposed list (a parallel to Greg KH's developer list,
but for end-users) probably wouldn't suffice either.  But it would be
relatively easy to create, and if it got big enough, and if some
manufacturers were hesitating about going open-source, it might tip a
scale or two.

In another message on this list, Greg KH says he has no objection to my
proposal but doesn't want to do it himself (a reasonable position given
the workload he's carrying already).  I'll try to set something up and
will ANNOUNCE it here if I succeed.

-- 
| G r e g  L o u i s         | gpg public key:         0x6D9E3E64 |
|  http://www.bgl.nu/~glouis |   (on my website or any keyserver) |
--
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/