sniffer技术原理及应用,包括编程方法和工具使用

Bertha 。 2022-08-24 01:30 10阅读 0赞

http://www.hacker.com.cn/ 2008-11-2 0:03:46 黑客防线

<table style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; empty-cells: show; border-collapse: collapse; font-size: 12px; table-layout: fixed; overflow-x: hidden; overflow-y: hidden; "> 
 <tbody> 
 <tr> 
 <td style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; text-align: center !important; "></td> 
 </tr> 
 <tr> 
 <td style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; text-align: left; font-size: 14px; line-height: 160%; "> 
 <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; font-size: 14px; line-height: 160%; ">
 sniffer技术原理及应用,包括编程方法和工具使用 
 </div></td> 
 </tr> 
 <tr> 
 <td style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; text-align: left; font-size: 14px; line-height: 160%; "> 
 <div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; font-size: 14px; line-height: 160%; ">
 sniffer中文翻译过来就是嗅探器，在当前网络技术中使用得非常得广泛。sniffer既可以做为网络故&nbsp; 
 障的诊断工具，也可以作为黑客嗅探和监听的工具。最近两年，网络监听(sniffer)技术出现了新的&nbsp; 
 重要特征。传统的sniffer技术是被动地监听网络通信、用户名和口令。而新的sniffer技术出现了主&nbsp; 
 动地控制通信数据的特点，把sniffer技术扩展到了一个新的领域。Sniffer 技术除了目前在传统的&nbsp; 
 网络侦测管理外，也开始被应用在资讯保全的领域。可以这样说，sniffer技术是一把双刃剑，如何&nbsp; 
 更好的利用它，了解它的一些特性，将能使这项技术更好的为我们带来便利。&nbsp; 
 sniffer的编程方法比较通用的有以下几种，1.winpcap 这是一个比较通用的库，相信做过抓包的&nbsp; 
 工具大多数人都不会太陌生 2.raw socket 在2000以后的版本都支持此项功能，2000 server有个网络监视器就是基于raw socket 3.tdi,ndis,spi,hook socket技术，这种技术比较大的不同是可以将包截取而不是仅仅获得包的一份拷贝。总的说来，一般以前两者居多。&nbsp; 
 我这里提的都还比较片面，更多的需要大家来补充。我办这个专题的目的是希望大家共同来了解，讨论sniffer技术，让更多的人参与进来，让大家知道，这个板块能够给大家带来真正想要的东西。&nbsp; 
 warton:&nbsp; 
 libpcap是个好东西,linux,windows下都能用，很多入侵检测之类的安全系统都是以这为核心。不&nbsp; 
 过我一直没用过它，不知道它的跨平台性如何？&nbsp; 
 要用spi的话，看看xfilter的代码和书，特别是那本书上讲得不错，可惜一直没用它做出什么东西来。&nbsp; 
 raw socket写的sniffer比较多，网上代码也很多！&nbsp; 
 昨天见csdn首页有几篇关于sniffer的文章，保存了，还没来得及看...&nbsp; 
 俺明天来说说目前常用的sniffer类工具和它们的技术实现！&nbsp; 
 
 csdn首页的两篇文章，大家可以看看,里面好像还有几篇，暂时找不到了&nbsp; 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.csdn.net/develop/article/21/21363.shtm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.csdn.net/develop/article/21/21363.shtm</a>&nbsp; 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.csdn.net/develop/article/21/21352.shtm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.csdn.net/develop/article/21/21352.shtm</a>&nbsp; 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.csdn.net/develop/article/15/15919.shtm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.csdn.net/develop/article/15/15919.shtm</a>&nbsp; 
 
 netsys2:&nbsp; 
 
 一）winpcap驱动简介&nbsp; 
 &nbsp;&nbsp;winpcap(windows packet capture)是windows平台下一个免费，公共的网络访问系统。开&nbsp; 
 
 发winpcap这个项目的目的在于为win32应用程序提供访问网络底层的能力。它提供了以下的各项&nbsp; 
 
 功能：&nbsp; 
 &nbsp;&nbsp;1&gt; 捕获原始数据报，包括在共享网络上各主机发送/接收的以及相互之间交换的数据报；&nbsp; 
 &nbsp;&nbsp;2&gt; 在数据报发往应用程序之前，按照自定义的规则将某些特殊的数据报过滤掉；&nbsp; 
 &nbsp;&nbsp;3&gt; 在网络上发送原始的数据报；&nbsp; 
 &nbsp;&nbsp;4&gt; 收集网络通信过程中的统计信息。&nbsp; 
 
 &nbsp;&nbsp;&nbsp; 
 
 winpcap的主要功能在于独立于主机协议（如TCP-IP)而发送和接收原始数据报。也就是说，winp&nbsp; 
 
 cap不能阻塞，过滤或控制其他应用程序数据报的发收，它仅仅只是监听共享网络上传送的数据报。因此，它不能用于QoS调度程序或个人防火墙。&nbsp; 
 
 &nbsp;&nbsp;目前，winpcap开发的主要对象是windows NT/2000/XP，这主要是因为在使用winpcap的&nbsp; 
 
 用户中只有一小部分是仅使用windows 95/98/Me，并且M$也已经放弃了对win9x的开发。因&nbsp; 
 
 此本文相关的程序T-ARP也是面向NT/2000/XP用户的。其实winpcap中的面向9x系统的概念和&nbsp; 
 
 NT系统的非常相似，只是在某些实现上有点差异，比如说9x只支持ANSI编码，而NT系统则提倡使&nbsp; 
 
 用Unicode编码。&nbsp; 
 
 zzhong2:&nbsp; 
 有个软件叫sniffer pro.可以作网管软件用,有很多功能,可监视网络运行情况,每台网内机器的数据&nbsp; 
 
 流量,实时反映每台机器所访问IP以及它们之间的数据流通情况,可以抓包,可对过滤器进行设置,以便&nbsp; 
 
 只抓取想要的包,比如POP3包,smtp包,ftp包等,并可从中找到邮箱用户名和密码,还有ftp用户名和&nbsp; 
 
 密码.它还可以在使用交换机的网络上监听,不过要在交换机上装它的一个软件.&nbsp; 
 还有一个简单的监听软件叫 Passwordsniffer,可截获邮箱用户名和密码,还有ftp用户名和密码,它&nbsp; 
 
 只能用在用HUB网络上&nbsp; 
 以上两个软件都可在小凤居上下载到 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.chinesehack.org/" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.chinesehack.org/</a>&nbsp; 
 
 
 warton:&nbsp; 
 libpcap的最新版本是0.7.2，下载很多（基于linux/unix）&nbsp; 
 winpcap的最新版本是3.0&nbsp; 
 这里有winpcap的源代码 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://download.pchome.net/php/dl.php?sid=11474" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://download.pchome.net/php/dl.php?sid=11474</a>&nbsp; 
 著名软件tcpdump及ids snort都是基于libpcap编写的，此外Nmap扫描器也是基于libpcap来捕&nbsp; 
 
 获目标主机返回的数据包的。&nbsp; 
 winpcap提供给用户两个不同级别的编程接口：一个基于libpcap的wpcap.dl，另一个是较底层的&nbsp; 
 
 packet.dll。对于一般的要与unix平台上libpcap兼容的开发来说，使用pacap.dll是当然的选择。&nbsp; 
 下面几个库是与lipcap相关的：&nbsp; 
 libnet1.0.2：数据包的发送个构造过程&nbsp; 
 libnids:实现了ids的一些　框架&nbsp; 
 libicmp：icmp数据包处理&nbsp; 
 
 
 
 
 一些著名的嗅探器：&nbsp; 
 tcpdump/windump:支持多种unix，后者支持windows。基于libpcap&nbsp; 
 Sniffit:unix,windows,libpcap&nbsp; 
 Ngrep:libpcap,unixwindows.可以用规则表达式，识别PPP,SLIP及FDDI数据包&nbsp; 
 Sniffer pro/NetXray:专业的协议分析工具，是NAI提供的网络分析方案中的一部分&nbsp; 
 其它：&nbsp; 
 Iris&nbsp; 
 LanExplorer&nbsp; 
 NetMOnitor&nbsp; 
 CommView&nbsp; 
 
 单一用途的噢探器&nbsp; 
 口令嗅：winsniffer,典型的黑客工具，嗅探并解析ftp,pop3,http,icq,smtp,telnet,IMAP,NNTP&nbsp; 
 
 等口令&nbsp; 
 password sniffer for NetHackerIII&nbsp; 
 
 专用　嗅探器：&nbsp; 
 SMB嗅探器：L0phtcrack，SMPRelay&nbsp; 
 TCP连接会话嗅探器:CommView ,Iris,Juggernaut&nbsp; 
 SSL嗅探器：SSLDump--sslv3/tls网络协议分析工具&nbsp; 
 RIDIUS嗅控器：一个基于udp的论证记账协议，Radiusniff是其代表&nbsp; 
 PPTP嗅　控器：Anger,PPTP-sniff(solaris)&nbsp; 
 SNMP嗅探器：Snmpsniff&nbsp; 
 
 交换网络嗅探器：Ettercap&nbsp; 
 综合：Dsniff&nbsp; 
 其它交换网络嗅探器：&nbsp; 
 snarp,parasite&nbsp; 
 
 嗅探对策.........&nbsp; 
 
 netsys2:&nbsp; 
 
 网络上流传的GUNIFFER是个基本的原型：&nbsp; 
 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://asp.6to23.com/nowcan/code/guniffer.zip" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://asp.6to23.com/nowcan/code/guniffer.zip</a>&nbsp; 
 
 void main(int argc, char ** argv)&nbsp; 
 
 {&nbsp; 
 
 int iErrorCode;&nbsp; 
 
 char RecvBuf[MAX_PACK_LEN] = {0};&nbsp; 
 
 usage();&nbsp; 
 
 if(GetCmdLine(argc, argv)==CMD_PARAM_HELP) exit(0);&nbsp; 
 
 //初始化SOCKET&nbsp; 
 
 WSADATA wsaData;&nbsp; 
 
 iErrorCode = WSAStartup(MAKEWORD(2,1),&amp;wsaData);&nbsp; 
 
 CheckSockError(iErrorCode, "WSAStartup");&nbsp; 
 
 SockRaw = socket(AF_INET , SOCK_RAW , IPPROTO_IP);&nbsp; 
 
 CheckSockError(SockRaw, "socket");&nbsp; 
 
 //获取本机IP地址&nbsp; 
 
 char FAR name[MAX_HOSTNAME_LAN];&nbsp; 
 
 iErrorCode = gethostname(name, MAX_HOSTNAME_LAN);&nbsp; 
 
 CheckSockError(iErrorCode, "gethostname");&nbsp; 
 
 struct hostent FAR * pHostent; //注意下面这三句，这里先对pHostent分配了一块&nbsp; 
 
 pHostent = (struct hostent * )malloc(sizeof(struct hostent));&nbsp; 
 
 //内存，然后有让它等于gethostbyname函数的返回&nbsp; 
 
 pHostent = gethostbyname(name); //值，但gethostbyname函数是自己在函数内部分配内&nbsp; 
 
 存的，因此上一句根本就是多余，把上一句删除后一切正常。但此程序用VC6编译运行都没有问题&nbsp; 
 
 ，不知为何？也许是VC6的编译器优化在起作用。&nbsp; 
 
 SOCKADDR_IN sa;&nbsp; 
 
 sa.sin_family = AF_INET;&nbsp; 
 
 sa.sin_port = htons(6000);&nbsp; 
 
 memcpy(&amp;sa.sin_addr.S_un.S_addr, pHostent-&gt;h_addr_list[0], pHostent-&gt;h_length);&nbsp; 
 
 free(pHostent); //由于前面分配内存的语句已经删除，所以这一句也要去掉，否则出错。感谢网&nbsp; 
 
 友 Heyuming 发现这个问题。&nbsp; 
 
 iErrorCode = bind(SockRaw, (PSOCKADDR)&amp;sa, sizeof(sa));&nbsp; 
 
 CheckSockError(iErrorCode, "bind");&nbsp; 
 
 //设置SOCK_RAW为SIO_RCVALL，以便接收所有的IP包&nbsp; 
 
 DWORD dwBufferLen[10] ;&nbsp; 
 
 DWORD dwBufferInLen = 1 ;&nbsp; 
 
 DWORD dwBytesReturned = 0 ;&nbsp; 
 
 iErrorCode=WSAIoctl(SockRaw, SIO_RCVALL,&amp;dwBufferInLen,&nbsp; 
 
 sizeof(dwBufferInLen),&nbsp; 
 
 &amp;dwBufferLen, sizeof(dwBufferLen),&amp;dwBytesReturned , NULL , NULL );&nbsp; 
 
 CheckSockError(iErrorCode, "Ioctl");&nbsp; 
 
 //侦听IP报文&nbsp; 
 
 while(1)&nbsp; 
 
 {&nbsp; 
 
 memset(RecvBuf, 0, sizeof(RecvBuf));&nbsp; 
 
 iErrorCode = recv(SockRaw, RecvBuf, sizeof(RecvBuf), 0);&nbsp; 
 
 CheckSockError(iErrorCode, "recv");&nbsp; 
 
 iErrorCode = DecodeIpPack(RecvBuf, iErrorCode);&nbsp; 
 
 CheckSockError(iErrorCode, "Decode");&nbsp; 
 
 }&nbsp; 
 
 }&nbsp; 
 
 它有2个不方便之处：&nbsp; 
 1）不能选择网卡&nbsp; 
 2）采用死循环方式读数据，改编到WINDOWS窗口模式下时有死机的感觉。&nbsp; 
 
 sevencat():&nbsp; 
 上次找了一些资料整理了一下，不过人气不旺，而且最近比较忙，暂时还没继续下去。&nbsp; 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://expert.csdn.net/Expert/topic/2299/2299615.xml?temp=.2761499" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://expert.csdn.net/Expert/topic/2299/2299615.xml?temp=.2761499</a>&nbsp; 
 WINDOWS网络包过滤技术&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;（原文 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.ndis.com/papers/winpktfilter.htm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.ndis.com/papers/winpktfilter.htm</a>）&nbsp; 
 一、user-mode网络包过滤&nbsp; 
 1、winsock分层service provider&nbsp; 
 参照Microsoft Platform SDK上有关文档和例子&nbsp; 
 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.microsoft.com/msdownload/platformsdk/sdkupdate/</a>）&nbsp; 
 这里有好几个microsoft lsp 例子，最新（可能最bug-free）的经常在这里能找到。需要知道的是&nbsp; 
 
 可以通过TDI调用核心TCPIP驱动，而且可以完全绕开WINSOCK，在大多数情况下这不是一个问&nbsp; 
 
 题。例如：QOS的实现可以在WINSOCK　LSP上。&nbsp; 
 然而，这样做的话，程序必须察看和操作每个包，而不能依靠WINSOCK　LSP，他们要以一种接&nbsp; 
 
 近核心态的方法来实现。&nbsp; 
 2、win2000包过滤接口&nbsp; 
 　　WIN2000包过滤接口提供了一种机制，这种机制允许用户态程序或者服务指定一系列的"过滤&nbsp; 
 
 原则"，这些过滤原则会被低层的TCPIP实现用来过滤包。这种过滤工主要是对IP原地址、目标地址、端口号（或者端口号范围）进行pass或者drop操作。&nbsp; 
 Windows Developer's Journal&nbsp; 
 《用iphlpapi.dll进行包过滤》作者：Ton plooy，October,2000,Volume 11, Number 10。&nbsp; 
 　　WIN2000提供了一个较好对TCPIP的可编程控制，其中包括包过滤。不幸的是，有关这个新&nbsp; 
 
 的API的文档并不是很容易能找到。这篇文章向你演示了怎样对特定IP地址或者特定TCP端口的包&nbsp; 
 
 进行阻塞的编程。&nbsp; 
 链接：www.wdj.com&nbsp; 
 上面这个例子的下载：ftp://ftp.wdj.com/pub/webzip/1110/plooy.zip&nbsp; 
 Hollis 的解决方案：&nbsp; 
 　　HTS　W2K　IpHook例子演示了IP过滤和它的HOOK　API，包含原文件，而且是免费的，&nbsp; 
 
 需要HtsCpp运行时库（免费），下载地址 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.hollistech.com/" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.hollistech.com/</a>&nbsp; 
 3、winsock替代DLL&nbsp; 
 　　在使用WINSOCK　LSP之前，唯一的办法是用自己的DLL取代微软的WINSOCK　DLL，假&nbsp; 
 
 如实现顺利的话，自己的DLL会接收用户的WINSOCK调用请求，然后还可以调用原来的WINSOC&nbsp; 
 
 K　DLL来处理。&nbsp; 
 　　不过这样的实现是比较费力的，其中有个困难就是微软的WINSOCK　DLL里面经常有一些未&nbsp; 
 
 公开的内部使用的函数，一个WINSOCK代替DLL至少要处理其中的一些未公开函数。&nbsp; 
 　　随着WINDOWS系统结构的变化，有些方面得到了加强，比如系统文件保护，这使得这种技术&nbsp; 
 
 变得不太可行。总的说来，使用WINSOCK　DLL替换不是一个坏主意。（Xfilter就是用的这种技&nbsp; 
 
 术，原代码可能在网上有流传，我以前看到过的）&nbsp; 
 二、kernel-mode网络包过滤&nbsp; 
 1、Transport Data Interface （TDI）&nbsp; 
 　　这主要是一个直接在核心TCPIP驱动上面的一层过滤驱动。在WINXP上TDI驱动是一种传统的&nbsp; 
 
 NT风格的驱动，使用了基于IRP的API，这里有两种方法来实现。&nbsp; 
 A、使用核心模式服务的IoAttachDeviceXYZ函数族在TDI上实现一个过滤。&nbsp; 
 B、对TDI驱动IRP　DISPATCH表进行过滤。&nbsp; 
 　　IoAttachDeviceXYZ函数在许多WINNT驱动开发的书上提到。这两种技术都需要对WINNT驱&nbsp; 
 
 动开发编程技术十分了解，对TDI函数也要相当的了解。&nbsp; 
 2、NDIS中间层（IM）&nbsp; 
 具体请看NDIS IM FAQ 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.pcausa.com/resources/ndisimfaq.htm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.pcausa.com/resources/ndisimfaq.htm</a>&nbsp; 
 3、WIN2000　FILTER－HOOK&nbsp; 
 　　请参照有关DDK文档，系统中只能有一个活动的Filter-Hook存在，这点使这种技术的使用有&nbsp; 
 
 严重的限制。（平时所见的drvipflt就是用的这个）&nbsp; 
 4、WIN2000　FIREWALL－HOOK　&nbsp; 
 　　Firewall-Hook Driver函数在文档里介绍得很少，而且在有些win2000版本中不可用。请参&nbsp; 
 
 照微软有关文档 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://msdn.microsoft.com/library/default.asp?url=/library/en-us</a>&nbsp; 
 
 /network/hh/network/firewall_3wfb.asp&nbsp; 
 5、NDIS－HOOKING　 （费尔防火墙就是用的这种技术吧，据我所知，虽然我没看过原码。）&nbsp; 
 NDIS-Hooking驱动拦截或者叫"HOOK"一些由NDIS封装程序导出的函数。虽然从实现手段上来&nbsp; 
 
 说有些不正规，但一个有系统的NDIS-Hooking过滤会非常有效。&nbsp; 
 另外：NDIS-Hooking过滤驱动有下面的好处：&nbsp; 
 A、容易安装（可以动态装卸，不过有时候会出问题，里面有些情况现在还未知。）&nbsp; 
 B、支持拨号-ppp适配器。&nbsp; 
 　　Ndis-Hooking技术在98和ME系统下非常有效和实用。在这些平台上，DDK文档和provide&nbsp; 
 
 d services都能很有用的帮你HOOK由Ndis wrapper导出的函数。&nbsp; 
 　　Ndis-Hooking技术在NT，2000和XP上同样有效和实用。这种技术很像核心模式的调试器。&nbsp; 
 
 文档支持较少，而且基本上不会被WHQL认证。&nbsp; 
 PCAUSA提供了一套NDIS　PIM驱动例子，这些例子能在现有的WIN平台上运行成功（从95到X&nbsp; 
 
 P）。地址 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www.pcausa.com/ndispim/Default.htm" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.pcausa.com/ndispim/Default.htm</a>&nbsp; 
 
 其他：&nbsp; 
 Network操作和进程信息：&nbsp; 
 　　有许多人想知道网络上的操作和WIN进程（就是应用程序啦）之间怎样联系起来，举例来说，&nbsp; 
 
 可能会想知道是哪个进程在一个特定的IP端口上发送或接收数据。&nbsp; 
 　　先不考虑这种技术是否有用，或者是否可靠，我们认为核心模式TCPIP驱动上层的过滤程序可&nbsp; 
 
 以处理这个问题。而TCPIP驱动下层的过滤程序根本看不到进程信息。特别要注意的是有些网络服&nbsp; 
 
 务操作生成一个新的进程attach到系统进程上的。在这种情况下进程信息并不能告诉我们原先是哪&nbsp; 
 
 个进程生成的。特别是单独在核心模式下的WIN服务（TDI客户）&nbsp; 
 　　最后，有必要看看下面的资料United States Patent 5,987,611; "System and&nbsp; 
 
 methodology for managing internet access on a per application basis for client&nbsp; 
 
 computers connected to the internet "&nbsp; 
 　　我们并不知道这项专利的价值，也不知道他是否能用在包过滤上。详情请参阅 
 <img src="http://www.hacker.com.cn/images/filetype/url.gif" style="border-style: initial; border-color: initial; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; vertical-align: middle; "> 
 <a href="http://www./" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; color: rgb(0, 0, 0); text-decoration: underline; " rel="nofollow">http://www.</a>&nbsp; 
 
 uspto.gov/patft/index.html&nbsp; 
 www.pcausa.com&nbsp; 
 
 ============================================&nbsp; 
 drvipflt具体解析，就是上面所提到的吧(2－3就是说的这东东）。&nbsp; 
 假定大家对驱动框架已经有了一定的理解。IRP分配程序如下：&nbsp; 
 NTSTATUS DrvDispatch(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp)&nbsp; 
 {&nbsp; 
 ...&nbsp; 
 &nbsp;&nbsp;switch (irpStack-&gt;MajorFunction)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 ...&nbsp; 
 &nbsp;&nbsp;case IRP_MJ_DEVICE_CONTROL:&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;ioControlCode = irpStack-&gt;Parameters.DeviceIoControl.IoControlCode;&nbsp; 
 
 &nbsp;&nbsp;&nbsp;&nbsp;switch (ioControlCode)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;// ioctl code to start filtering&nbsp; 
 &nbsp;&nbsp;//这里可以从用户模式程序发送这样的请求。&nbsp; 
 &nbsp;&nbsp;//直接用DeviceIoControl这个函数，就像下面这样调用就可&nbsp; 
 
 以了吧，我想。&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 
 //DeviceIoControl(drivehandle,START_IP_HOOK,NULL,0,NULL,0,&amp;bytereturned,NU&nbsp; 
 
 LL)&nbsp; 
 &nbsp;&nbsp;case START_IP_HOOK:&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;//这个应该是最主要的函数了。&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SetFilterFunction(cbFilterFunction);&nbsp; 
 
 &nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;// ioctl to stop filtering&nbsp; 
 &nbsp;&nbsp;case STOP_IP_HOOK:&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;SetFilterFunction(NULL);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// ioctl to add a filter rule&nbsp; 
 &nbsp;&nbsp;case ADD_FILTER:&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;if(inputBufferLength == sizeof(IPFilter))&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;IPFilter *nf;&nbsp; 
 
 &nbsp;&nbsp;nf = (IPFilter *)ioBuffer;&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;AddFilterToList(nf);&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;// ioctl to free filter rule list&nbsp; 
 &nbsp;&nbsp;case CLEAR_FILTER:&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;ClearFilterList();&nbsp; 
 
 &nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;default:&nbsp; 
 &nbsp;&nbsp;Irp-&gt;IoStatus.Status =&nbsp; 
 
 STATUS_INVALID_PARAMETER;&nbsp; 
 
 
 &nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;&nbsp;&nbsp;break;&nbsp; 
 ...&nbsp; 
 }&nbsp; 
 SetFilterFunction(cbFilterFunction)可能是最重要的一个程序了。具体如下：&nbsp; 
 实际上这个做法相当在系统中注册了一个回调函数。&nbsp; 
 NTSTATUS SetFilterFunction(PacketFilterExtensionPtr filterFunction)&nbsp; 
 {&nbsp; 
 NTSTATUS status = STATUS_SUCCESS, waitStatus=STATUS_SUCCESS;&nbsp; 
 UNICODE_STRING filterName;&nbsp; 
 PDEVICE_OBJECT ipDeviceObject=NULL;&nbsp; 
 PFILE_OBJECT ipFileObject=NULL;&nbsp; 
 
 PF_SET_EXTENSION_HOOK_INFO filterData;&nbsp; 
 
 KEVENT event;&nbsp; 
 IO_STATUS_BLOCK ioStatus;&nbsp; 
 PIRP irp;&nbsp; 
 
 //首先获得一个设备指针。&nbsp; 
 //first of all, we have to get a pointer to IpFilterDriver Device&nbsp; 
 RtlInitUnicodeString(&amp;filterName, DD_IPFLTRDRVR_DEVICE_NAME);&nbsp; 
 status = IoGetDeviceObjectPointer(&amp;filterName,STANDARD_RIGHTS_ALL,&nbsp; 
 
 &amp;ipFileObject, &amp;ipDeviceObject);&nbsp; 
 if(NT_SUCCESS(status))&nbsp; 
 {&nbsp; 
 //一些初始化工作，填充filterData。&nbsp; 
 //initialize the struct with functions parameters&nbsp; 
 filterData.ExtensionPointer = filterFunction;&nbsp; 
 
 //we need initialize the event used later by the IpFilterDriver to&nbsp; 
 
 signal us&nbsp; 
 //when it finished its work&nbsp; 
 KeInitializeEvent(&amp;event, NotificationEvent, FALSE);&nbsp; 
 
 //这个就是最重要的注册回调函数过程。DDK中具体讲述是这样的&nbsp; 
 //IOCTL_PF_SET_EXTENSION_POINTER registers filter-hook callback functions to&nbsp; 
 
 the IP filter driver&nbsp; 
 //to inform the IP filter driver to call those filter hook callbacks for every IP packet&nbsp; 
 //that is received or transmitted. Also, IOCTL_PF_SET_EXTENSION_POINTER&nbsp; 
 
 clears filter-hook&nbsp; 
 //callback functions from the IP filter driver. （看到了吧，最后一句话，注册新的回调函&nbsp; 
 
 数，就将原先的清除掉了，&nbsp; 
 //所以说系统中只存在一个这样的驱动有用。）&nbsp; 
 //we build the irp needed to establish fitler function这个地方仅&nbsp; 
 
 仅是生成这样的IRP，并没有注册&nbsp; 
 irp =&nbsp; 
 
 IoBuildDeviceIoControlRequest(IOCTL_PF_SET_EXTENSION_POINTER,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 &nbsp;&nbsp;ipDeviceObject,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 (PVOID) &amp;filterData,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 sizeof(PF_SET_EXTENSION_HOOK_INFO),&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 NULL,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 0,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 FALSE,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 &amp;event,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 &amp;ioStatus);&nbsp; 
 
 
 if(irp != NULL)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;// we send the IRP&nbsp; 
 &nbsp;&nbsp;//这个地方才是真正的注册呀。&nbsp; 
 &nbsp;&nbsp;status = IoCallDriver(ipDeviceObject, irp);&nbsp; 
 
 &nbsp;&nbsp;//and finally, we wait for "acknowledge" of&nbsp; 
 
 IpDriverFilter&nbsp; 
 &nbsp;&nbsp;if (status == STATUS_PENDING)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;waitStatus = KeWaitForSingleObject(&amp;event,&nbsp; 
 
 Executive, KernelMode, FALSE, NULL);&nbsp; 
 
 &nbsp;&nbsp;if (waitStatus != STATUS_SUCCESS )&nbsp; 
 
 {}&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 
 &nbsp;&nbsp;status = ioStatus.Status;&nbsp; 
 
 &nbsp;&nbsp;if(!NT_SUCCESS(status)){}&nbsp; 
 }&nbsp; 
 
 else&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;//if we cant allocate the space, we return the&nbsp; 
 
 corresponding code error&nbsp; 
 &nbsp;&nbsp;status = STATUS_INSUFFICIENT_RESOURCES;&nbsp; 
 
 }&nbsp; 
 
 if(ipFileObject != NULL)&nbsp; 
 &nbsp;&nbsp;ObDereferenceObject(ipFileObject);&nbsp; 
 
 ipFileObject = NULL;&nbsp; 
 ipDeviceObject = NULL;&nbsp; 
 }&nbsp; 
 
 else&nbsp; 
 
 return status;&nbsp; 
 }&nbsp; 
 //真正的过滤函数是这个，在最早的IRPdispatch里面传递的这个函数。&nbsp; 
 //这个函数就是系统传递了一个包头和包内容和包长度之类的东西，你可以在里面进行一些处理，&nbsp; 
 //假如你想让这个包通过的话，就返回PF_FORWARD，或者你不想让包通过的话，就返回PF_D&nbsp; 
 
 ROP就拦住了。是不是&nbsp; 
 //听起来很简单，&nbsp; 
 PF_FORWARD_ACTION cbFilterFunction(IN unsigned char *PacketHeader,IN&nbsp; 
 
 unsigned char *Packet, IN unsigned int PacketLength, IN unsigned int&nbsp; 
 
 RecvInterfaceIndex, IN unsigned int SendInterfaceIndex, IN unsigned long&nbsp; 
 
 RecvLinkNextHop, IN unsigned long SendLinkNextHop)&nbsp; 
 {&nbsp; 
 IPPacket *ipp;&nbsp; 
 TCPHeader *tcph;&nbsp; 
 UDPHeader *udph;&nbsp; 
 
 int countRule=0;&nbsp; 
 
 struct filterList *aux = first;&nbsp; 
 
 //we "extract" the ip Header&nbsp; 
 ipp=(IPPacket *)PacketHeader;&nbsp; 
 
 // dprintf("Source: %x/nDestination: %x/nProtocol: %d", ipp-&gt;ipSource,&nbsp; 
 
 ipp-&gt;ipDestination, ipp-&gt;ipProtocol);&nbsp; 
 
 //TCP -&gt; protocol = 6&nbsp; 
 //we accept all packets of established connections&nbsp; 
 if(ipp-&gt;ipProtocol == 6)&nbsp; 
 {&nbsp; 
 tcph=(TCPHeader *)Packet;&nbsp; 
 
 // dprintf("FLAGS: %x/n", tcph-&gt;flags);&nbsp; 
 
 //if we havent the bit SYN activate, we pass the packets&nbsp; 
 if(!(tcph-&gt;flags &amp; 0x02))&nbsp; 
 &nbsp;&nbsp;return PF_FORWARD;&nbsp; 
 }&nbsp; 
 
 //otherwise, we compare the packet with our rules&nbsp; 
 while(aux != NULL)&nbsp; 
 {&nbsp; 
 // dprintf("Comparing with Rule %d", countRule);&nbsp; 
 
 //if protocol is the same....&nbsp; 
 if(aux-&gt;ipf.protocol == 0 || ipp-&gt;ipProtocol ==&nbsp; 
 
 aux-&gt;ipf.protocol)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;//we look in source Address&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.sourceIp != 0 &amp;&amp; (ipp-&gt;ipSource &amp;&nbsp; 
 
 aux-&gt;ipf.sourceMask) != aux-&gt;ipf.sourceIp)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;aux=aux-&gt;next;&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;countRule++;&nbsp; 
 &nbsp;&nbsp;continue;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;// we look in destination address&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.destinationIp != 0 &amp;&amp; (ipp-&gt;ipDestination&nbsp; 
 
 &amp; aux-&gt;ipf.destinationMask) != aux-&gt;ipf.destinationIp)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;aux=aux-&gt;next;&nbsp; 
 
 &nbsp;&nbsp;countRule++;&nbsp; 
 &nbsp;&nbsp;continue;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;//if we have a tcp packet, we look in ports&nbsp; 
 &nbsp;&nbsp;//tcp, protocol = 6&nbsp; 
 &nbsp;&nbsp;if(ipp-&gt;ipProtocol == 6)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.sourcePort == 0 ||&nbsp; 
 
 tcph-&gt;sourcePort == aux-&gt;ipf.sourcePort)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.destinationPort == 0&nbsp; 
 
 || tcph-&gt;destinationPort == aux-&gt;ipf.destinationPort) //puerto tcp destino&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;//now we decided what&nbsp; 
 
 to do with the packet&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;if(aux-&gt;ipf.drop)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 return PF_DROP;&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;else&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
 return PF_FORWARD;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;//udp, protocol = 17&nbsp; 
 &nbsp;&nbsp;else if(ipp-&gt;ipProtocol == 17)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;udph=(UDPHeader *)Packet;&nbsp; 
 
 &nbsp;&nbsp;if(aux-&gt;ipf.sourcePort == 0 ||&nbsp; 
 
 udph-&gt;sourcePort == aux-&gt;ipf.sourcePort)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.destinationPort == 0&nbsp; 
 
 || udph-&gt;destinationPort == aux-&gt;ipf.destinationPort)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;//now we decided what&nbsp; 
 
 to do with the packet&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;if(aux-&gt;ipf.drop)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return&nbsp; 
 
 PF_DROP;&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;else&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return&nbsp; 
 
 PF_FORWARD;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;&nbsp; 
 &nbsp;&nbsp;else&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;//for other packet we dont look more and&nbsp; 
 
 ....&nbsp; 
 &nbsp;&nbsp;//now we decided what to do with the&nbsp; 
 
 packet&nbsp; 
 &nbsp;&nbsp;if(aux-&gt;ipf.drop)&nbsp; 
 &nbsp;&nbsp;return PF_DROP;&nbsp; 
 &nbsp;&nbsp;else&nbsp; 
 &nbsp;&nbsp;return PF_FORWARD;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 }&nbsp; 
 
 //compare with the next rule&nbsp; 
 countRule++;&nbsp; 
 aux=aux-&gt;next;&nbsp; 
 }&nbsp; 
 
 //we accept all not registered&nbsp; 
 return PF_FORWARD;&nbsp; 
 }&nbsp; 
 
 winpcap也是用的NDIS，将自己注册为一个协议处理驱动。(在原代码的driverentry里面能看到)&nbsp; 
 
 又：上面这个drvipflt这个代码的过滤部分不知道大家是不是看起来很熟悉，是的，是抄的那个nu&nbsp; 
 
 mege的驱动开发包里面的一个包过滤程序里的，看来老外也是喜欢到处抄的。&nbsp; 
 
 ruike:&nbsp; 
 读研的时候专门搞过nids，因此对winpcap可以说是情有独钟，这个东东确实好用，但也确实很烦&nbsp; 
 
 人，它有一个致命的缺陷就是只适用于共享式以太网络，对于交换式网络下的数据则无能为力，我&nbsp; 
 
 专门做过测试，在使用交换机连接的局域网下，只能监听到本网段内的数据，而对于来自其他网段&nbsp; 
 
 的数据则无法监听，除非你把probe接到交换机之前或者接到交换机的console口上，不过那样的&nbsp; 
 
 弊端是显而易见的。&nbsp; 
 所以，winpcap的应用还是很有局限性的！&nbsp; 
 
 kingzai:&nbsp; 
 实现交换网络的嗅探也有不少方法的&nbsp; 
 1.将你的抓包程序放在网关或代理服务器上，这样抓到整个局域网的包。&nbsp; 
 2.对交换机实行端口映射，将该端口的数据包全部映射到某个监控机器上。&nbsp; 
 3.在交换机和路由器之间连接一个HUB,这样数据将以广播的方式发送。&nbsp; 
 4.实行ARP欺骗，即在你的机器上实现整个包的转发，不过会降低整个局域网的效率。&nbsp; 
 
 warton:&nbsp; 
 嗅探对策：&nbsp; 
 光说嗅探了，我说说反嗅探吧：）&nbsp; 
 1.检查网内的主机上是否将网卡设置为混合模式（有很多工具可以做到，AntiSniff,Promiscan,S&nbsp; 
 
 entinel等）&nbsp; 
 2.对EtterCap这样的交换网络嗅探器（进行ARP欺骗），可以采用防止ARP欺骗的方法来对待&nbsp; 
 3.SSH加密通道&nbsp; 
 4.SSL&nbsp; 
 5.VPN&nbsp; 
 6.PGP等&nbsp; 
 
 目前这用利用网卡混合模式来进行sniffer的软件看来作用不太大了，所以应该多考虑交换网络的可&nbsp; 
 
 行办法：&nbsp; 
 
 MAC Flooding,MAC Duplicating,ARP欺骗等等&nbsp; 
 这些方法实现起来就不怎么容易了，欢迎有兴趣的朋友提供相关的资料，呵呵！&nbsp; 
 
 netsys:&nbsp; 
 难道没人用过RAW SOCKET 吗？&nbsp; 
 虽然WINPCP功能很大，但RAW SOCKET可以让你直接了SOCKET的原生机制。&nbsp; 
 实际上我提的那两个问题是很容易解决的。。&nbsp; 
 
 netsys2:&nbsp; 
 对于一些混合模式的SNIFFER，大多采用发送特殊ARP包的方式，正确的网卡不会响应，而处于&nbsp; 
 
 混合模式的网卡则会响应。&nbsp; 
 
 当然，ARP与IP处于同层，因此你不能用RAW SOCKET完成，你需WinPcap支持工作。&nbsp; 
 
 下面是部分代码&nbsp; 
 
 AnsiString msgStatus;&nbsp; 
 extern TArpFuncParam wParams;&nbsp; 
 
 int BuildARPPacket(PArpPacket ArpPacket, unsigned char *dst_etheraddr,&nbsp; 
 &nbsp;&nbsp;unsigned char *src_etheraddr, int ar_op, unsigned&nbsp; 
 
 char *ar_sha,&nbsp; 
 &nbsp;&nbsp;unsigned char *ar_sip, unsigned char *ar_tha,&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;unsigned char *ar_tip,unsigned short int ar_hw)&nbsp; 
 {&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;eth_dst_addr), dst_etheraddr, ETH_ADD_LEN);&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;eth_src_addr), src_etheraddr, ETH_ADD_LEN);&nbsp; 
 ArpPacket-&gt;eth_type = htons(ETH_TYPE_ARP);&nbsp; 
 ArpPacket-&gt;ar_hrd = htons(ar_hw);&nbsp; 
 ArpPacket-&gt;ar_pro = htons(ARP_PRO_IP);&nbsp; 
 ArpPacket-&gt;ar_hln = ARP_ETH_ADD_SPACE;&nbsp; 
 ArpPacket-&gt;ar_pln = ARP_IP_ADD_SPACE;&nbsp; 
 ArpPacket-&gt;ar_op = htons(ar_op);&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;ar_sha), ar_sha, ARP_ETH_ADD_SPACE);&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;ar_spa), ar_sip, ARP_IP_ADD_SPACE);&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;ar_tha), ar_tha, ARP_ETH_ADD_SPACE);&nbsp; 
 memcpy(&amp;(ArpPacket-&gt;ar_tpa), ar_tip, ARP_IP_ADD_SPACE);&nbsp; 
 memset(ArpPacket-&gt;eth_pad, 32, ETH_PADDING_ARP);&nbsp; 
 return(EXIT_SUCCESS);&nbsp; 
 }&nbsp; 
 int OpenAdapter(LPADAPTER *lpAdapter)&nbsp; 
 {&nbsp; 
 *lpAdapter =&nbsp; 
 
 PacketOpenAdapter(wParams.AdapterList[wParams.SelectedAdapter]);&nbsp; 
 
 if(!(*lpAdapter) || ((*lpAdapter)-&gt;hFile == INVALID_HANDLE_VALUE))&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Error : unable to open the driver.";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 &nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 }&nbsp; 
 return(EXIT_SUCCESS);&nbsp; 
 }&nbsp; 
 void CloseAdapter(LPADAPTER lpAdapter)&nbsp; 
 {&nbsp; 
 PacketCloseAdapter(lpAdapter);&nbsp; 
 
 }&nbsp; 
 void GetLocalMAC(LPADAPTER lpAdapter, unsigned char *ether_addr)&nbsp; 
 {&nbsp; 
 
 ULONG IoCtlBufferLength = (sizeof(PACKET_OID_DATA) + sizeof(ULONG) - 1);&nbsp; 
 PPACKET_OID_DATA OidData;&nbsp; 
 
 OidData = (struct _PACKET_OID_DATA *)malloc(IoCtlBufferLength);&nbsp; 
 OidData-&gt;Oid = OID_802_3_CURRENT_ADDRESS;&nbsp; 
 OidData-&gt;Length = 6;&nbsp; 
 if(PacketRequest(lpAdapter, FALSE, OidData) == FALSE)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;memcpy(ether_addr, 0, 6);&nbsp; 
 else&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;memcpy(ether_addr, OidData-&gt;Data, 6);&nbsp; 
 free(OidData);&nbsp; 
 }&nbsp; 
 int GetARPReply(LPPACKET lpPacket, unsigned char *iptarget, unsigned char&nbsp; 
 
 *result)&nbsp; 
 {&nbsp; 
 unsigned short int ether_type;&nbsp; 
 unsigned char&nbsp;&nbsp;&nbsp;&nbsp; ipsender[4];&nbsp;&nbsp;&nbsp; 
 unsigned int&nbsp;&nbsp;&nbsp;&nbsp; off=0;&nbsp; 
 unsigned int&nbsp;&nbsp;&nbsp;&nbsp; tlen;&nbsp; 
 struct bpf_hdr&nbsp;&nbsp; *hdr;&nbsp; 
 char&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *pChar;&nbsp; 
 char&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *buf;&nbsp; 
 
 buf = (char *)lpPacket-&gt;Buffer;&nbsp; 
 hdr = (struct bpf_hdr *)(buf + off);&nbsp; 
 tlen = hdr-&gt;bh_caplen;&nbsp; 
 off += hdr-&gt;bh_hdrlen;&nbsp;&nbsp;&nbsp; 
 pChar = (char*)(buf + off);&nbsp; 
 off = Packet_WORDALIGN(off + tlen);&nbsp; 
 memcpy(ðer_type, pChar + 12, 2);&nbsp; 
 ether_type = ntohs(ether_type);&nbsp; 
 if(ether_type == ETH_TYPE_ARP)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;memcpy(ipsender, pChar + 28, 4);&nbsp; 
 &nbsp;&nbsp;if((iptarget[0] == ipsender[0])&amp;&amp;(iptarget[1] == ipsender[1])&amp;&amp;&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;(iptarget[2] == ipsender[2])&amp;&amp;(iptarget[3] == ipsender[3]))&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;memcpy(result, pChar + 22, 6);&nbsp; 
 &nbsp;&nbsp;else&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 }&nbsp; 
 else&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 return(EXIT_SUCCESS);&nbsp; 
 }&nbsp; 
 int CheckPROMode(LPADAPTER lpAdapter, unsigned char *iptarget, unsigned char&nbsp; 
 
 *remotemac)&nbsp; 
 {&nbsp; 
 
 LPPACKET lpPacketRequest;&nbsp; 
 LPPACKET lpPacketReply;&nbsp; 
 char&nbsp;&nbsp; buffer[256000];&nbsp; 
 
 TArpPacket ArpPacket;&nbsp; 
 unsigned char magicpack[ETH_ADD_LEN]= {0xFF,0xFF,0xFF,0xFF,0xFF,0xFE};&nbsp; 
 unsigned char mactarget[ARP_ETH_ADD_SPACE];&nbsp; 
 
 DWORD timestamp = 0;&nbsp; 
 int numPacks = 0;&nbsp; 
 /* Init fields */&nbsp; 
 memset(mactarget, 0, 6);&nbsp; 
 /* Allocate PACKET structure for ARP Request packet */&nbsp; 
 if((lpPacketRequest = PacketAllocatePacket()) == NULL)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Error : failed to allocate the LPPACKET structure..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 &nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 }&nbsp; 
 
 /* Init packet structure */&nbsp; 
 memset(&amp;ArpPacket, 0, sizeof(TArpPacket));&nbsp; 
 
 /* Build ARP Request packet */&nbsp; 
 BuildARPPacket(&amp;ArpPacket, magicpack, wParams.srcMAC, ARP_OP_REQUEST,&nbsp; 
 
 wParams.srcMAC, wParams.srcIPAdd, mactarget, iptarget,wParams.ar_hw);&nbsp; 
 
 /* Init ARP Request packet */&nbsp; 
 PacketInitPacket(lpPacketRequest, &amp;ArpPacket, sizeof(ArpPacket));&nbsp; 
 
 /* Set number of ARP Request packets to send */&nbsp; 
 if(PacketSetNumWrites(lpAdapter, 1) == FALSE)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Warning : unable to send more than one packet in a single write..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 }&nbsp; 
 /* Set hardware filter to directed mode */&nbsp; 
 if(PacketSetHwFilter(lpAdapter, NDIS_PACKET_TYPE_DIRECTED) == FALSE)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus ="Warning: unable to set directed mode..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 }&nbsp; 
 /* Set a 512K buffer in the driver */&nbsp; 
 if(PacketSetBuff(lpAdapter, 512000) == FALSE)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Error: unable to set the kernel buffer..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 &nbsp;&nbsp;PacketFreePacket(lpPacketRequest);&nbsp; 
 &nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 }&nbsp; 
 /* Set a 1 second read timeout */&nbsp; 
 if(PacketSetReadTimeout(lpAdapter, -1) == FALSE)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Warning: unable to set the read tiemout..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 }&nbsp; 
 
 /* Allocate PACKET structure for ARP Reply packet */&nbsp; 
 if((lpPacketReply = PacketAllocatePacket()) == NULL)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;msgStatus = "Error: failed to allocate the LPPACKET structure..";&nbsp; 
 &nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 &nbsp;&nbsp;PacketFreePacket(lpPacketRequest);&nbsp; 
 &nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 }&nbsp; 
 /* Init ARP Reply packet */&nbsp; 
 PacketInitPacket(lpPacketReply, (char*)buffer, 256000);&nbsp; 
 /* Allocate memory for remote MAC address */&nbsp; 
 timestamp = GetTickCount();&nbsp; 
 
 /* Main capture loop */&nbsp; 
 for(;;)&nbsp; 
 {&nbsp; 
 &nbsp;&nbsp;if(numPacks &lt; wParams.numPacks)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;/* Send packet */&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;if(PacketSendPacket(lpAdapter, lpPacketRequest, TRUE) == FALSE)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;msgStatus ="Error : unable to send the packets..";&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;PacketFreePacket(lpPacketRequest);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;PacketFreePacket(lpPacketReply);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;/* Free packet */&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;PacketFreePacket(lpPacketRequest);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;numPacks += 1;&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;/* Capture the packets */&nbsp; 
 &nbsp;&nbsp;if(PacketReceivePacket(lpAdapter, lpPacketReply, TRUE) == FALSE)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;msgStatus = "Error: PacketReceivePacket failed..";&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;SHOWSTAT(msgStatus);&nbsp; 
 PacketFreePacket(lpPacketReply);&nbsp; 
 &nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 &nbsp;&nbsp;if(lpPacketReply-&gt;ulBytesReceived &gt; 0)&nbsp; 
 &nbsp;&nbsp;if(GetARPReply(lpPacketReply, iptarget, remotemac) == EXIT_SUCCESS)&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;break;&nbsp; 
 &nbsp;&nbsp;if((GetTickCount() - timestamp) &gt; wParams.delay)&nbsp; 
 &nbsp;&nbsp;{&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;PacketFreePacket(lpPacketReply);&nbsp; 
 &nbsp;&nbsp;&nbsp;&nbsp;return(EXIT_FAILURE);&nbsp; 
 &nbsp;&nbsp;}&nbsp; 
 }&nbsp; 
 /* Free packet */&nbsp; 
 PacketFreePacket(lpPacketReply);&nbsp; 
 return(EXIT_SUCCESS);&nbsp; 
 }&nbsp; 
 sunxufei:&nbsp; 
 哦，交换机是以MAC地址进行交换的，不是IP那一层的，要IP已经路由器了&nbsp; 
 现在交换机便宜了，因此以后你想用sniffer抓密码概率不大了，不过还能多公司仍然是交换机和H&nbsp; 
 
 UB一起用的，这样小范围内是有效地，至于ADSL CABLE FTTB,我的FTTB是用华为设计的设备&nbsp; 
 
 ,呵呵,不仅仅工网IP,只有我和交换机两个MAC(这次中国人干的不错),没希望找到第三者,很安全,但&nbsp; 
 
 不都这样安全,很多人的网络还是很糟糕的.&nbsp; 
 很多加密协议可以用来提高安全性,但老的POP3,SMTP,HTTP,FTP这种协议应用广泛,不可能在短&nbsp; 
 
 时间内完全取代,而且加密也是有待价的,所以对于要求较高的场合,才会加密.&nbsp; 
 不过sniffer不是给大家偷密码用的,我当初用来学习网络,看看包的样子,后来就用来当作网管工具,&nbsp; 
 
 分析网络的健康与否,其实这样的话,你知道,很有可能sniffer就是接在我需要探测的网络上,听诊器&nbsp; 
 
 吗,到处都听听,呵呵,因此即使用了交换机,sniffer仍然是有用处的,但不是抓密码!!&nbsp; 
 Wincap很简单,大3的学生不要怕,去他的网站看看,有例子的,VC6编译,BCB也行的,把lib的格式转&nbsp; 
 
 换一下,不过写这种程序,你最好先熟悉协议,很多协议在linux里有现成的源代码,主要是一些struct&nbsp; 
 
 吧,移植时注意VC可不是gcc,有些c的高级语法,编译选项要注意,否则差一个byte你就得不到正确的&nbsp; 
 
 结果.&nbsp; 
 如果你搞不到sniffer,Win2000 Server也有网络包查看器的,不比sniffer强大,但简单的东西入 
 </div></td> 
 </tr> 
 </tbody> 
</table>

所属分类: [内网渗透][Link 1] 所属专题:

[Link 1]: http://www.hacker.com.cn/article/list_79.html