home.social

#win32k — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #win32k, aggregated by home.social.

  1. Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well!

    winbindex.m417z.com/?arch=insi
    winbindex.m417z.com/?arch=insi

    You can find both the x64 version and the ARM64 version available for download there.

    #rust #rustlang #windows #microsoft #win32k #reversing #reverseengineering

  2. Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well!

    winbindex.m417z.com/?arch=insi
    winbindex.m417z.com/?arch=insi

    You can find both the x64 version and the ARM64 version available for download there.

    #rust #rustlang #windows #microsoft #win32k #reversing #reverseengineering

  3. Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well!

    winbindex.m417z.com/?arch=insi
    winbindex.m417z.com/?arch=insi

    You can find both the x64 version and the ARM64 version available for download there.

    #rust #rustlang #windows #microsoft #win32k #reversing #reverseengineering

  4. Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well!

    winbindex.m417z.com/?arch=insi
    winbindex.m417z.com/?arch=insi

    You can find both the x64 version and the ARM64 version available for download there.

    #rust #rustlang #windows #microsoft #win32k #reversing #reverseengineering

  5. Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well!

    winbindex.m417z.com/?arch=insi
    winbindex.m417z.com/?arch=insi

    You can find both the x64 version and the ARM64 version available for download there.

    #rust #rustlang #windows #microsoft #win32k #reversing #reverseengineering

  6. Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too...

    Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so far???

    #rust #rustlang #windows #microsoft #reversing #reverseengineering #win32k

  7. Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too...

    Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so far???

    #rust #rustlang #windows #microsoft #reversing #reverseengineering #win32k

  8. Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too...

    Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so far???

    #rust #rustlang #windows #microsoft #reversing #reverseengineering #win32k

  9. Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too...

    Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so far???

    #rust #rustlang #windows #microsoft #reversing #reverseengineering #win32k

  10. Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too...

    Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so far???

    #rust #rustlang #windows #microsoft #reversing #reverseengineering #win32k

  11. Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) !

    There's a "shim" function named Win32kRS::RegionCore_bInside_point inside win32kbase that takes care of actually calling into the Rust function exports table. There's a whole bunch more of these new functions, one for each exported function from the Rust code, under the namespace Win32kRS.

    #rust #rustlang #windows #reversing #reverseengineering #microsoft #win32k

  12. Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) !

    There's a "shim" function named Win32kRS::RegionCore_bInside_point inside win32kbase that takes care of actually calling into the Rust function exports table. There's a whole bunch more of these new functions, one for each exported function from the Rust code, under the namespace Win32kRS.

    #rust #rustlang #windows #reversing #reverseengineering #microsoft #win32k

  13. Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) !

    There's a "shim" function named Win32kRS::RegionCore_bInside_point inside win32kbase that takes care of actually calling into the Rust function exports table. There's a whole bunch more of these new functions, one for each exported function from the Rust code, under the namespace Win32kRS.

    #rust #rustlang #windows #reversing #reverseengineering #microsoft #win32k

  14. Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) !

    There's a "shim" function named Win32kRS::RegionCore_bInside_point inside win32kbase that takes care of actually calling into the Rust function exports table. There's a whole bunch more of these new functions, one for each exported function from the Rust code, under the namespace Win32kRS.

    #rust #rustlang #windows #reversing #reverseengineering #microsoft #win32k

  15. Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) !

    There's a "shim" function named Win32kRS::RegionCore_bInside_point inside win32kbase that takes care of actually calling into the Rust function exports table. There's a whole bunch more of these new functions, one for each exported function from the Rust code, under the namespace Win32kRS.

    #rust #rustlang #windows #reversing #reverseengineering #microsoft #win32k

  16. @[email protected] Woot! The #Rust port of (parts of) #win32k is now public! Coming to an Insider build... Soon 😉

  17. @[email protected] Woot! The #Rust port of (parts of) #win32k is now public! Coming to an Insider build... Soon 😉

  18. @[email protected] Woot! The port of (parts of) is now public! Coming to an Insider build... Soon 😉

  19. @[email protected] Woot! The #Rust port of (parts of) #win32k is now public! Coming to an Insider build... Soon 😉