Search:

Type: Posts; User: fez_ajer

Search: Search took 0.00 seconds.

  1. Replies
    80
    Views
    55,160

    Now that you say it that way...

    It makes much more sense as to WHY ;)

    It just doesn't really offer any real protection. That's good for our case, but suxxor for the OS itself.

    Fez
  2. Replies
    80
    Views
    55,160

    Are you sure about MmGetPhysicalAddress?

    Hrm... I've never actually checked but I would think that MmMapIoSpace would fail on virtual protect rather than MmGetPhysicalAddress... The reasons being:

    1) MmGetPhysicalAddress supposedly...
  3. Replies
    80
    Views
    55,160

    Ok, here's the jig...

    I've implemented an IOCTL function which uses nothing but win32 kernel calls to read the memory. This means no hardcoding of list pointers and such. It also means it should work without...
  4. Replies
    80
    Views
    55,160

    Here's an interesting function...

    Lost,

    I think that KeGetCurrentProcess *MAY* be an undocumented export. I also know that this function:

    PsLookupProcessByProcessId(IN ULONG ulProcId,OUT struct _EPROCESS ** pEProcess);

    Is...
  5. Replies
    80
    Views
    55,160

    If you just need any EPROCESS struct

    I believe there is a kernel function:

    KeGetCurrentProcess()

    which returns PEPROCESS for the process which calls the IOCTL. That should indeed do the trick to avoid hardcoding the list head. ...
  6. Replies
    80
    Views
    55,160

    This should help

    Hey, Lost...

    Nice job with what you're doing. I think this is heading in the right direction.

    I thought I'd drop this lil tidbit to you, as I think it could be useful. Basically, it's an...
Results 1 to 6 of 6