Skip to content
View 3itch's full-sized avatar
:atom:
i miss atom
:atom:
i miss atom

Block or report 3itch

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. checkm8 checkm8 Public

    bypassing intel txt's tboot integrity checks via coreboot shim

    C 63 4

  2. icekit icekit Public

    I/O Cache-As-Ram + AMD x86_64 cache line locking | Mirror of https://codeberg.org/3itch/icekit

    C 14 3

  3. Hyperion: An already-done-before ana... Hyperion: An already-done-before analysis of Roblox's "anti-cheat"
    1
    #### Before I start I would like to mention a few things.
    2
    
                  
    3
    Unlike how kernel-space code can't particularly defend against other kernel code, this is not true for user-space. User-space code can actually defend against user code. This is because of natively supported things like user-space virtual memory spaces, which prevent direct access to the memory of other processes. This feature is called process isolation and is typically provided by the Operating System.
    4
    
                  
    5
    Not only process isolation, but ASLR as well, which in layman terms just randomizes the memory addresses in processes. This thwarts any prediction of target addresses due to prevention of static addresses. ASLR also has a kernel version called KASLR as well. This just does the same thing, but in kernel-space processes.