Code Analysis of the Linux Wireless Team's ath5k Driver
,----[ Quote ]
| The Software Freedom Law Center (SFLC) carried out an exhaustive, detailed,
| diachronic review of the Linux ath5k driver (“ath5k-driver”).
`----
http://www.softwarefreedom.org/resources/2007/ath5k-code-analysis.html
Related:
Software Freedom Law Center Completes Review of Linux Wireless Code
,----[ Quote ]
| This is not the first time that SFLC has worked with the Linux Wireless
| developers. In July, SFLC announced that it had performed a confidential
| audit of the open source Atheros driver and determined that no portion of it
| was illegally copied from Atheros' proprietary code.
`----
http://www.linuxelectrons.com/news/mobile/12375/software-freedom-law-center-completes-review-linux-wireless-code
http://tinyurl.com/2oua9m
Continued Atheros Discussions
,----[ Quote ]
| Disagreement continued as to whether or not the BSD license allows the
| addition of new copyrights on unmodified or minimally modified code. Another
| disagreement was over the continued existence of improperly licensed files in
| developer source code repository histories from when BSD licensed files had
| been changed to the GPL, a problem since fixed.
`----
http://kerneltrap.org/Linux/Continued_Atheros_Discussions
SFLC on Atheros Driver Issue
,----[ Quote ]
| Let me therefore point out one last time that if the threats of litigation
| and bluster about crime and malpractice--none of which has the slightest
| basis in fact or law--were withdrawn, we would be able to resume detailed
| communication with everyone who has a stake in the outcome.
`----
http://kerneltrap.org/Linux/SFLC_on_Atheros_Driver_Issue
http://kerneltrap.org/mailarchive/linux-kernel/2007/9/16/261061
Atheros Driver Developments
http://kerneltrap.org/OpenBSD/Atheros_Driver_Developments
Relicensing: what's legal and what's right
,----[ Quote ]
| In the end, distributing versions of the ath5k driver under GPLv2 (with the
| requisite copyright attributions maintained) is something which the Linux
| community is entitled to do. Anybody who does not like more restrictive
| conditions being applied to BSD-licensed code is well advised to avoid using
| the BSD license to begin with. But the legal ability to do something does not
| make that something the right course of action. Only the developers who have
| worked on the ath5k driver have the right to decide which license they will
| use, but it's worth saying that allowing the BSD community to make use of
| work done on the ath5k driver would be a friendly gesture and an
| acknowledgment of the value of the code we got from them. The benefits from
| such an act would likely outweigh any cost associated with allowing unwanted
| proprietary use of the code which has been added to this driver.
`----
http://lwn.net/Articles/247872/
Open Source coders caught stealing Open Source code
http://www.theinquirer.net/default.aspx?article=38746
FCC ignores more than 100 years of wisdom
,----[ Quote ]
| In 1883 French cryptographer Auguste Kerckhoffs published a set of six
| design principles for military encryption systems. The second of these
| principles is generally known today under the observation that security
| through obscurity is not security. The Federal Communications Commission
| (FCC) seems not to have read the history books or to be aware of how its
| sister federal agencies develop security standards....
`----
http://www.infoworld.nl/idgns/bericht.phtml?id=002570DE00740E1800257313005EC092
The FCC, FOSS, and software radios: a mixed bag
,----[ Quote ]
| After studying the new rules -- published in the Federal Register last month
| and taking effect today -- the SFLC concluded that the laws are not
| FOSS-restrictive because they "apply to hardware manufacturers who distribute
| SDR devices, regardless if they use FOSS in them or not." And the Center says
| that since the rules specifically mention the GNU/Linux operating system, the
| FCC is actually acknowledging the importance of open source.
`----
http://www.linux.com/feature/116769
|
|
