• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            S.l.e!ep.¢%

            像打了激速一樣,以四倍的速度運轉,開心的工作
            簡單、開放、平等的公司文化;尊重個性、自由與個人價值;
            posts - 1098, comments - 335, trackbacks - 0, articles - 1
              C++博客 :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理

            Writing a device driver for Windows

            Posted on 2009-10-30 11:04 S.l.e!ep.¢% 閱讀(591) 評論(1)  編輯 收藏 引用 所屬分類: RootKit

            Writing a device driver for Windows

            In order to write a device driver for windows, one needs the device driver development kit (ddk) and a c compiler.
            According to this article, a device driver's maximum size is 960MB on Windows XP (100MB on NT4, 220MB on Win2K).

            Setting up the environment

            A proper environment must be setup. Use setenv (which ships with the ddk) to set the environment variables (and what not) to build a driver:
            C:\>programme\ntddk\bin\setenv \programme\ntddk.
            The argument that is given to setenv must point to the directory under which the ddk is installed.

            makefile

            The directory that contains the sources for the device driver must have a file called makefile and another file called sources. For a simple device driver, it is sufficient to have one single line in the makefile:
            !INCLUDE $(NTMAKEENV)\makefile.def
            

            sources

            This file actually contains the names of the files to be compiled:
            TARGETNAME=kamel
            TARGETPATH=obj
            TARGETTYPE=DRIVER
            
            SOURCES=kamel.c writeEvent.c kamelMsg.rc
            
            C_DEFINES=-DUNICODE -DSTRICT
            
            kamel.c is the code for the driver itself, writeEvent.c contains a function that can be called to write messages to the system event log (see below) and kamelMsg.rc contains the strings that are written

            Writing the driver

            I call the driver we're going to write Kamel. In german, this will then be called Kameltreiber which is a pun german speaking people will understand. So, we're creating (according to the sources file) a file called kamel.c. The first lines contain the includes we need:
            #include "ntddk.h"
            #include "writeEvent.h"
            #include "kamelMsg.h"
            
            ntddk.h must always be included, writeEvent.h contains the declaration of WriteEvent (which is a function to write events, of course) and kamelMsg.h (being created by the message compiler) contains the identifiers of the strings we want to write using WriteEvent.
            Each driver needs a DriverEntry function which is called when the driver is loaded:
            Now, we use write the forward declarations together with the pragmas alloc_text. They indicate wheather or not the function is pageable.
            #define BUFFERSIZE 1024
            #define BUFFERTAG  'kmlb'
            
            typedef struct _KAMEL_DRIVER_EXTENSION {
              char buffer[BUFFERSIZE];
            } KAMEL_DRIVER_EXTENSION, *PKAMEL_DRIVER_EXTENSION;
            
            KAMEL_DRIVER_EXTENSION* driverExtension=0;
            
            
            NTSTATUS DriverEntry  (IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath);
            NTSTATUS CreateCamel  (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            NTSTATUS ReadCamel    (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            NTSTATUS WriteCamel   (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            NTSTATUS ShutdownCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            NTSTATUS CleanupCamel (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            NTSTATUS IoCtlCamel   (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
            VOID     CmlUnload    (IN PDRIVER_OBJECT  DriverObject);
            
            
            #ifdef ALLOC_PRAGMA
            #pragma alloc_text(INIT, DriverEntry)
            #pragma alloc_text(PAGE, CreateCamel) 
            #pragma alloc_text(PAGE, ReadCamel) 
            #pragma alloc_text(PAGE, WriteCamel) 
            #pragma alloc_text(PAGE, ShutdownCamel)
            #pragma alloc_text(PAGE, IoCtlCamel)
            #pragma alloc_text(PAGE, CmlUnload)
            #endif
            
            NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath) {
            
              UNICODE_STRING nameString, linkString;
              PDEVICE_OBJECT deviceObject;
              NTSTATUS status;
            
              WriteEvent(MSG_DRIVER_ENTRY,DriverObject,NULL);
            
              RtlInitUnicodeString(&nameString, L"\\Device\\Kamel");
            
              status = IoCreateDevice(
                DriverObject, 
                sizeof(65533),
                &nameString, 
                0, //FILE_DEVICE_UNKNOWN,
                0, 
                FALSE, 
                &deviceObject);
            
              if (!NT_SUCCESS(status))
                return status;
            
            
              deviceObject->Flags |= DO_DIRECT_IO;
              deviceObject->Flags &= ~DO_DEVICE_INITIALIZING;
            
            
              RtlInitUnicodeString(&linkString, L"\\DosDevices\\Kamel");
              status = IoCreateSymbolicLink (&linkString, &nameString);
            
              if (!NT_SUCCESS(status)) {
                IoDeleteDevice (DriverObject->DeviceObject);
                return status;
              }
            
            
              DriverObject->MajorFunction[IRP_MJ_CREATE]         = CreateCamel;
              DriverObject->MajorFunction[IRP_MJ_READ]           = ReadCamel;
              DriverObject->MajorFunction[IRP_MJ_WRITE]          = WriteCamel;
              DriverObject->MajorFunction[IRP_MJ_SHUTDOWN]       = ShutdownCamel;
              DriverObject->MajorFunction[IRP_MJ_DEVICE_CONTROL] = IoCtlCamel;
              
              DriverObject->DriverUnload=CmlUnload;
            
              // ExAllocatePool is obsolete and ExAllocatePoolWithTag should be used.
              driverExtension = ExAllocatePool(NonPagedPool, sizeof (KAMEL_DRIVER_EXTENSION));
            
              if(!driverExtension) {
                WriteEvent(MSG_NO_IOALLOCATEDRIVEROBJECTEXTENSION, DriverObject, NULL);
                return STATUS_INSUFFICIENT_RESOURCES;
              }
            
              RtlZeroMemory(driverExtension->buffer, BUFFERSIZE);
            
              RtlCopyBytes (driverExtension->buffer, "123456789012345", 16);
            
              return STATUS_SUCCESS;
            }
            
            DriverEntry first writes an Event (using WriteEvent, explained later) so it can be verified that DriverEntry indeed was called. Then, the actual device is created using IoCreateDevice and initialized.

            Setting Up Major Functions

            An Application communicates with a driver with the driver's Major Functions. These are set in the drivers array of function pointers MajorFunction.

            User Visible Name for the driver

            In order to create a user-visible name for the device just created, IoCreateSymbolicLink is called.

            Allocating Pool Memory

            The driver allocates some Pool Memory with ExAllocatePool.
            By the way, Paged and Non-Paged Pool Memory sized can be adjusted with the registry keys HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\(Non)PagedPoolSize. The Value specified is the size in bytes.

            Programming the Major Functions

            In DriverEntry, the Major Functions IRP_MJ_CREATE, IRP_MJ_READ, IRP_MJ_WRITE, IRP_MJ_SHUTDOWN, IRP_MJ_DEVICE_CONTROL were set. Here are the actual functions they point to:

            IRP_MJ_CREATE

            This function is called when a file using this deivce is created. In Win32Api, Devices are opened using CreateFile which then routes in the function associated with IRP_MJ_CREATE.
            NTSTATUS CreateCamel (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
              WriteEvent(MSG_CREATE,(PVOID)DeviceObject,NULL);
            
              IoCompleteRequest(Irp,IO_NO_INCREMENT);
              return  STATUS_SUCCESS;
            }
            

            IRP_MJ_READ

            NTSTATUS ReadCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
              PUCHAR                      currentAddress;
              PIO_STACK_LOCATION          irpStack;
            
              WriteEvent(MSG_READ,DeviceObject,NULL);
            
              if (!driverExtension) {
                WriteEvent(MSG_DRIVEREXTISNULLINREAD,DeviceObject,NULL);
                IoCompleteRequest(Irp, IO_NO_INCREMENT);
                return STATUS_INSUFFICIENT_RESOURCES;
              }
              irpStack = IoGetCurrentIrpStackLocation(Irp);
            
              if (irpStack->MajorFunction == IRP_MJ_READ) {
                currentAddress = MmGetSystemAddressForMdlSafe(Irp->MdlAddress, NormalPagePriority);
            
                if (!currentAddress) {
                  WriteEvent(MSG_MMGETSYSTEMADDRESS,DeviceObject,NULL);
                  IoCompleteRequest(Irp, IO_NO_INCREMENT);
                  return STATUS_SUCCESS;
                }
                RtlMoveMemory(currentAddress, 
                driverExtension->buffer+irpStack->Parameters.Read.ByteOffset.LowPart,
                irpStack->Parameters.Read.Length);
              }
              else {
                WriteEvent(MSG_MAJORFUNC_NOT_READ,DeviceObject,NULL);
              }
            
              IoCompleteRequest(Irp, IO_NO_INCREMENT);
              return STATUS_SUCCESS;
            }
            
            A driver should call IoGetCurrentIrpStackLocation in its IRP function to receive a pointer to a IO_STACK_LOCATION structure.
            MmGetSystemAddressForMdlSafe is a macro. It returns a virtual address to non system-space for the buffer described by the MDL.

            IRP_MJ_WRITE

            NTSTATUS WriteCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
              PUCHAR                      currentAddress;
              PIO_STACK_LOCATION          irpStack;
            
              if (!driverExtension) {
                IoCompleteRequest(Irp, IO_NO_INCREMENT);
                return STATUS_INSUFFICIENT_RESOURCES;
              }
            
              irpStack = IoGetCurrentIrpStackLocation(Irp);
            
              if (irpStack->MajorFunction == IRP_MJ_WRITE) {
                currentAddress = MmGetSystemAddressForMdlSafe(Irp->MdlAddress, NormalPagePriority);
            
                if (!currentAddress) {
                  IoCompleteRequest(Irp, IO_NO_INCREMENT);
                  return STATUS_SUCCESS;
                }
            
                RtlMoveMemory(driverExtension->buffer+irpStack->Parameters.Write.ByteOffset.LowPart,
                    currentAddress, irpStack->Parameters.Write.Length);
              }
              else {
                WriteEvent(MSG_MAJORFUNC_NOT_READ,DeviceObject,NULL);
              }
            
              IoCompleteRequest(Irp, IO_NO_INCREMENT);
              return STATUS_SUCCESS;
            }
            

            IRP_MJ_SHUTDOWN

            NTSTATUS ShutdownCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
              WriteEvent(MSG_SHUTDOWN,DeviceObject,NULL);
              IoCompleteRequest(Irp, IO_NO_INCREMENT);
              return STATUS_SUCCESS;
            }
            

            IRP_MJ_DEVICE_CONTROL

            NTSTATUS IoCtlCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
              WriteEvent(MSG_IOCTL,DeviceObject,NULL);
              IoCompleteRequest(Irp, IO_NO_INCREMENT);
              return STATUS_SUCCESS;
            }
            

            The unload function

            VOID CmlUnload (IN PDRIVER_OBJECT  DriverObject) {
              UNICODE_STRING linkString;
            
              WriteEvent(MSG_DRIVERUNLOAD, DriverObject, NULL);
              ExFreePool(driverExtension);
              RtlInitUnicodeString (&linkString, L"\\DosDevices\\Kamel");
              IoDeleteSymbolicLink (&linkString);
              IoDeleteDevice(DriverObject->DeviceObject);
            }
            

            Writing Events from a Device Driver

            It is possible to write strings from the driver into the system event box (which then can be viewed with the event viewer (eventvwr.exe). It is not straight forward however and the following steps must each be done.

            The Message File

            First, a message file must be created, having the suffix .mc, that contains each possible string you want to output and also assignes a unique id to these strings. A sample is given here:
            MessageID    = 1
            Severity     = Informational
            SymbolicName = MSG_DRIVER_ENTRY
            Language     = English
            Driver Entry
            .
            MessageID    = 2
            Severity     = Informational
            SymbolicName = MSG_CREATE
            Language     = English
            Create
            .
            
            Each Entry must be followed by a single dot on its own line. In this sample, the unique Id is associated with the symbolic name MSG_DRIVER_ENTRY and the String "Driver Entry". If you take a look at DriverEntry above, you'll see that I call WriteEvent with the symbolic name MSG_DRIVER_ENTRY.
            The Message File then is to be compiled with the message compiler mc: mc KamelMsg.mc on the command line. This produces a file called MessageFile.rc. KamelMsg.rc must be included in the sources file. It also creates the file KamelMsg.h which must be included to have the constants.
            This is still not sufficient. Also a string entry must be created in the Registry under HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\<driverName>\EventMessageFile. The string must point to the .dll or .sys into which the messages were compiled, in our case: %SystemRoot%\System32\Drivers\Kamel.sys

            WriteEvent

            BOOLEAN WriteEvent(IN NTSTATUS ErrorCode , IN PVOID IoObject,IN PIRP Irp) {
              PIO_ERROR_LOG_PACKET Packet;
              PIO_STACK_LOCATION IrpStack;
              PWCHAR pInsertionString;
              STRING AnsiInsertString;
              UNICODE_STRING UniInsertString;
            
              UCHAR PacketSize;
            
              PacketSize = sizeof(IO_ERROR_LOG_PACKET);
            
              Packet = IoAllocateErrorLogEntry(IoObject,PacketSize);
              if (Packet == NULL) return FALSE;
            
              Packet->ErrorCode         = ErrorCode;
              Packet->UniqueErrorValue  = 0,
              Packet->RetryCount        = 0;
              Packet->SequenceNumber    = 0;
              Packet->IoControlCode     = 0;
              Packet->DumpDataSize      = 0;
              
              if (Irp!=NULL) {
                 IrpStack=IoGetCurrentIrpStackLocation(Irp);
                 Packet->MajorFunctionCode = IrpStack->MajorFunction;
                 Packet->FinalStatus = Irp->IoStatus.Status;
              } 
              else {
                 Packet->MajorFunctionCode = 0;
                 Packet->FinalStatus       = 0;
              }
            
              IoWriteErrorLogEntry(Packet);
              return TRUE;
            }
            

            WriteEvent.h

            BOOLEAN WriteEvent(IN NTSTATUS ErrorCode , IN PVOID IoObject,IN PIRP Irp); 
            #pragma alloc_text(PAGE, WriteEvent)
            

            Entries in the registry

            The driver must be registred with the registry: Create a this key HKLM\System\CurrentControlSet\Services\<driverName> and add the following keys: ErrorControl, Group, Start, Tag and Type.

            Feedback

            # re: Writing a device driver for Windows  回復  更多評論   

            2009-10-30 15:20 by 溪流
            mark. thx.
            噜噜噜色噜噜噜久久| 亚洲精品国产字幕久久不卡| 99久久成人国产精品免费| 少妇久久久久久被弄到高潮| 亚洲伊人久久综合影院| 人妻精品久久无码专区精东影业| 97精品国产91久久久久久| 久久久青草青青国产亚洲免观| 久久久久青草线蕉综合超碰| 久久精品国产亚洲AV无码娇色| 久久99亚洲综合精品首页| 亚洲色欲久久久综合网东京热| 国产69精品久久久久9999| 久久精品国产亚洲av麻豆图片 | 久久精品一区二区| 国产一区二区精品久久凹凸| 亚洲精品乱码久久久久66| 九九精品99久久久香蕉| 无夜精品久久久久久| 精品久久久久久亚洲| 久久亚洲AV成人出白浆无码国产| 久久av免费天堂小草播放| 久久久精品一区二区三区| 亚洲AV无码成人网站久久精品大| 久久五月精品中文字幕| 一本色道久久88加勒比—综合| 国产69精品久久久久99尤物| 久久精品国产亚洲av麻豆小说 | 久久99国产精品尤物| 亚洲国产成人久久综合一区77| 欧美亚洲色综久久精品国产| 色老头网站久久网| 久久精品这里只有精99品| 伊人久久综合热线大杳蕉下载| 久久国产乱子伦精品免费强| 久久久久亚洲AV无码网站| 久久夜色精品国产噜噜麻豆| 色偷偷久久一区二区三区| 久久综合国产乱子伦精品免费| 东方aⅴ免费观看久久av| 久久久久青草线蕉综合超碰|