Yes, there are plans to amend the security model: we are aware that a sniffing system must give restricted access to its features. However, this isn't among the priorities at the moment, so I think it will not be added in the very short period. At the moment, we are focusing on performance and monitoring. Obviously, patches are welcome and will be included in the future versions.
Loris ----- Original Message ----- From: "Kevin Gilbert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 12:28 AM Subject: [WinPcap-users] Security and WinPcap A few days ago, I posted a message and received no reply. Hence, at the risk of being impolite, I am posting it again - this time with the reason for the post. I have developed an educational package (called WinNOS) that, within the Windows environment, visually demonstrates the various protocols of the TCP / IP suite. WinNOS contains around 65,000 lines of Visual C++ code and uses the IBM / Microsoft "Data Link Control protocol" (ACSLAN / DLC.SYS) for its network interface. As you may know, this API has some serious problems and some design deficiencies that complicate the design of WinNOS and limit what it can provide. WinPcap appears to solve all my problems, with only one issue - security. In the environment where WinNOS will be used the workstations can / will be powered off by students, and the students will not have Administrator privileges. Therefore, I repeat my original post: --- This may be an oft asked question, but... Regarding FAQ #7, "Do I need to be Administrator in order to execute programs based on WinPcap on Windows NT/2000/XP?" Are there any plans to amend the security model? --- Kev Gilbert TAFE Lecturer in IT Phone: +61 08 8946 6282 Fax: +61 08 8946 6667 Mobile: 0419 206 146 Email: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
