#
#asahi-re · 2026-05-13 08:48
svenyour approach seems to be „looking for any reason to disassemble something“ while we prefer „looks for any reason NOT to disassemble anything and use that as a last resort“
#asahi-re · 2026-05-13 08:47
svenbut why do we care?
#asahi-re · 2026-05-13 08:44
StanfordAppliedCyber[m]I haven't touched them at all aside from the sptm firmware, but say the agx firmware could be nice for figuring out what the structs are exactly
#asahi-re · 2026-05-13 08:43
StanfordAppliedCyber[m]question, how much are we allowed to disasm the firmware blobs?
#asahi-re · 2026-05-13 06:47
fl0_id*researcher
#asahi-re · 2026-05-13 06:47
fl0_idtbh, even as legal research, there often isn't a clearly defined line. so it would still be a risk assessment at the end
#asahi-re · 2026-05-13 05:12
StanfordAppliedCyber[m]some of it is definitely useful, it'll all need a bit of a refactor to fit, and some things will still need to be cleanroomed, but I'll discuss this further when my code works and i've cleaned it up
#asahi-re · 2026-05-13 04:51
StanfordAppliedCyber[m]i'll see how it works
#asahi-re · 2026-05-13 04:51
StanfordAppliedCyber[m]brain extra small
#asahi-re · 2026-05-13 04:51
StanfordAppliedCyber[m]and...... I honestly didn't know we had pagetable stuff in m1n1
#asahi-re · 2026-05-13 04:51
StanfordAppliedCyber[m]understood
#asahi-re · 2026-05-13 04:29
svenagain, we’re not trying to cut corners here and since none of us are lawyers we’re being extra careful when possible
#asahi-re · 2026-05-13 04:28
svenif it’s pagetable stuff why not just use the code we already have in m1n1?
#asahi-re · 2026-05-13 00:59
StanfordAppliedCyber[m]that said yes, this could be done by someone else, as i said, boring page table walking, i'll document the endpoints if that's what we come to
#asahi-re · 2026-05-13 00:59
StanfordAppliedCyber[m]even the proxyclient which doesn't even have to be linked to main m1n1 if we don't want it to be? i understand things end users need, like pmgr, smp bringabsolutely should not be using this, but what i don't get is this is absolutely a development tool, no regular asahi user is going to be running macos under a hypervisor, not to mention m1n1 is entirely MIT licensed so it actually is apsl compatible
#asahi-re · 2026-05-13 00:57
JamesCalligeros[m]either reimplement the functionality or document it and let someone else do it. we arent here to cut corners and attract apple's ire
#asahi-re · 2026-05-13 00:56
JamesCalligeros[m]that notwithstanding, the APSL is just not compatible with the GPL so we cant just import code licenced under it into m1n1 wholesale
#asahi-re · 2026-05-13 00:56
JamesCalligeros[m]"tooling" is throwaway/one-shot stuff like the AGX shader disassembler or the scipy thingy i use to trim zeroes out of FIRs. the hypervisor is not "dev tooling" in that sense and is a major component of m1n1, which is software that we release and distribute to users as part of the project
#asahi-re · 2026-05-13 00:51
StanfordAppliedCyber[m]that said even if this isn't allowed most of it is boring page table walking stuff, truly nothing interesting aside from the 20 lines of stuff i mentioned earlier
#asahi-re · 2026-05-13 00:50
StanfordAppliedCyber[m]can we more rigorously define "actual release of the project" then? because this is an "Internal tools intended only for exploration and not to be released to end-users" with the explicit allow for "we can host such changes as an Asahi Linux repo"
#asahi-re · 2026-05-13 00:48
JamesCalligeros[m]we are happy for you to use Apple's code for experimentation and "tooling" but we cannot just integrate chunks of XNU into m1n1
#asahi-re · 2026-05-13 00:48
StanfordAppliedCyber[m]yeah, this isn't an official release, it's not going to end users, it's exclusively for developers
#asahi-re · 2026-05-13 00:48
StanfordAppliedCyber[m]that's also why i'm asking
#asahi-re · 2026-05-13 00:48
StanfordAppliedCyber[m]i'm aware apsl is copyleft
#asahi-re · 2026-05-13 00:48
JamesCalligeros[m]"but they cannot become an actual release of the project."
#asahi-re · 2026-05-13 00:47
StanfordAppliedCyber[m]actual release of the project.
#asahi-re · 2026-05-13 00:47
StanfordAppliedCyber[m]> Internal tools intended only for exploration and not to be released to end-users are allowed to use APSL code, including taking APSL releases directly and modifying them, as long as all licensing requirements are met. For example, taking an APSL release, modifying it to aid in reverse engineering, and using the result back in macOS is fine, and we can host such changes as an Asahi Linux repo, but they cannot become an
#asahi-re · 2026-05-13 00:46
nicolas17"In particular, be careful of open source dumps from Apple, as they are often licensed under the APSL, which is not GPL compatible. Asahi Linux does not allow any APSL code to be used directly"
#asahi-re · 2026-05-13 00:46
nicolas17that's in the policy too
#asahi-re · 2026-05-13 00:45
JamesCalligeros[m]apple's code is not permissively licenced. you need to reimplement the logic or document the logic and let someone else do it.
#asahi-re · 2026-05-13 00:45
JamesCalligeros[m]no, that is never okay
#asahi-re · 2026-05-13 00:26
StanfordAppliedCyber[m]@ someone who actually knows what they're talking about when it comes to copyright, i'm tainted as to SPTM, i've extensively disasm'd it, but am I allowed to push code strictly copy pasted from old xnu versions that implement the exact logic? like verbatim ctrl + c ctrl + v from apsl licensed source
#asahi-re · 2026-05-13 00:14
StanfordAppliedCyber[m]which may not even be copyrightable and trivial to clean room if it is
#asahi-re · 2026-05-13 00:14
StanfordAppliedCyber[m]I think the amount of code that doesn't involve stuff that you can take verbatim from xnu is incredibly small, like literally under 20 lines small
#asahi-re · 2026-05-13 00:08
StanfordAppliedCyber[m]good news for the port then, anything i ctrl c from the xnu kernel is specifically allowed by RE policy :)
#asahi-re · 2026-05-13 00:08
StanfordAppliedCyber[m]in hindsight, extremely obvious
#asahi-re · 2026-05-13 00:08
StanfordAppliedCyber[m]....i should have RTFM'd before brute forcing so much of the sptm code, looks like half of this was just xnu code previously
#asahi-re · 2026-05-11 20:02
jannausounds like an additional pmu setting for m3 ultra and m4+
#asahi-re · 2026-05-11 20:00
chaos_princesswait, no, this one is new, we had a "restore power state/stay powered off" bit
#asahi-re · 2026-05-11 19:59
chaos_princesspmu nvmem bit, for some reason i thought we already had it
#asahi-re · 2026-05-11 19:57
nicolas17https://support.apple.com/en-us/125517 new nvram variable?
#asahi-re · 2026-05-11 17:56
user890104Ghidra
#asahi-re · 2026-05-11 16:31
habibyhello all, what are your favorite tools to use when reverse engeneering?
#asahi-re · 2026-05-11 08:19
svenhuh, I would’ve expected at least the wkdm compression stuff next to genter/exit
#asahi-re · 2026-05-11 06:13
StanfordAppliedCyber[m]i checked for undocumented instructions in the kcache (via really stupid script) and couldn't find any
#asahi-re · 2026-05-10 07:59
StanfordAppliedCyber[m]if/when the kernel mode custom instructions become a problem i'll likely need some help there-- like the answer is obviously emulate them via hypercall but figuring out what they do exactly would be difficult for me
#asahi-re · 2026-05-10 07:57
StanfordAppliedCyber[m]oh, right, forgot about the userspace being the same
#asahi-re · 2026-05-10 07:40
svenit should be possible to disable most extensions in userspace as well simply because vmapple userspace is the same and can’t use any extensions either
#asahi-re · 2026-05-10 07:36
chaos_princesswkdm stuff has a sw fallback, you can disable it that way
#asahi-re · 2026-05-10 07:00
StanfordAppliedCyber[m]maybe this will be a problem, maybe it won't

plus ›