From owner-freebsd-questions@FreeBSD.ORG Thu Aug 3 15:56:58 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F401A16A4DD for ; Thu, 3 Aug 2006 15:56:57 +0000 (UTC) (envelope-from bob.middaugh@comcast.net) Received: from alnrmhc11.comcast.net (alnrmhc11.comcast.net [204.127.225.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB2B543D45 for ; Thu, 3 Aug 2006 15:56:57 +0000 (GMT) (envelope-from bob.middaugh@comcast.net) Received: from freebsd (c7144428.state.nj.us[199.20.68.40]) by comcast.net (alnrmhc11) with SMTP id <20060803155656b1100n88dfe>; Thu, 3 Aug 2006 15:56:56 +0000 From: Bob To: FreeBSD Questions Content-Type: text/plain Date: Thu, 03 Aug 2006 11:57:28 -0400 Message-Id: <1154620649.7963.19.camel@freebsd> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: NDISulate, Win32 driver & centrino exploits X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bob.middaugh@comcast.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Aug 2006 15:56:58 -0000 Hi everyone, I was reading this: http://isc.sans.org/diary.php?storyid=1535&rss and http://support.intel.com/support/wireless/wlan/sb/CS-023068.htm My question is how is a FreeBSD box with NDISulator, or a linux box with ndiswrapper, affected by these exploits? I'm guessing that since linux and FreeBSD don't execute pe files, and their api's are probably similar that I can *lump* them together in my question. If that's not the case, I apologize...and in turn don't really care about the linux side of my question. I don't write code, so I don't know how all that works. I have FreeBSD on my Dell D600. I would use ndisulator, and the windows driver because there's no support for the 2200BG under FreeBSD. Or is there, and I'm missing something??? Apparently, from at least the 1st of the three exploits noted on the intel site above, the vulnerability exists in the windows driver. A cracker could exploit the vulnerabilities which could "potentially lead to remote code execution and system control." Appreciate any insight anyone has on this. Thanks, Bob