Hello, Possibly some of you will have read the news about "Hijacking a Macbook in 60 Seconds or Less"[1]. At this time I was searching a wireless card for my server and I wonder how this can affect to the combination FreeBSD+ath(4). The ath_hal page states that FreeBSD use a binary driver and I think it is located in this file[2]. Unlike OpenBSD which affirms that they have reverse engineering[3] the drivers would I be at risk if I use atheros based wireless cards with FreeBSD? all comments will be appreciated. Thank you. [1] blog.washingtonpost.com/securityfix/2006/08/hijacking_a_macbook_in_60_seco_1.html [2] freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/dev/ath/public/i386-elf.hal.o.uu [3] onlamp.com/pub/a/bsd/2006/04/27/openbsd-3_9.html
In message <44DB6E98.8010701@fadesa.es>, =?ISO-8859-1?Q?=22Jos=E9_M=2E_Fandi=F1 o=22?= writes:> Unlike OpenBSD which affirms that they have reverse engineering[3] >the drivers would I be at risk if I use atheros based wireless cards >with FreeBSD?The Atheros driver in FreeBSD is maintained and compiled by Sam Leffler, who has been around since BSD 4.2 in the early eighties sometimes. I trust Sam. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
In message <20060811112511.T45647@fledge.watson.org>, Robert Watson writes:>Something worth observing here is that many modern device drivers, especially >more complex cards with significant offload of functionality to the card, have >closed source components [...]Not to mention regulatory requirements that the hardware not be configured in certain parts of spectrum or power levels. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.