#
#asahi-re · 2022-06-17 10:11
millenialhackerIs not bullet proof but does is job. You may find some difference in pointers size (for some reason the script assume pointers of 4-bytes instead of 8-bytes)
#asahi-re · 2022-06-17 10:10
millenialhackersven: https://github.com/0x36/ghidra_kernelcache
#asahi-re · 2022-06-17 10:10
millenialhackerlet me see the name
#asahi-re · 2022-06-17 10:10
millenialhackersven I found one that uses the output of another tool (which I do not remember) to help symbolicate the kernel
#asahi-re · 2022-06-17 09:37
svenmarcan: didn't you have some ghidra script somewhere to deal with all those annoying vtable calls? can you point me to that one again?
#asahi-re · 2022-06-17 06:14
sventhere was also one xnu release that contained more debug crap than usual (like that llvm bitcode for some kernel stuff)
#asahi-re · 2022-06-17 04:44
marcana lot of that is related to what our installer does, I probably could've really used that test script if I'd known about it before writing it...
#asahi-re · 2022-06-17 04:44
marcantons of references to the mythical bless2cli and bootabilityutil there... I wish we had those :)
#asahi-re · 2022-06-17 04:43
marcanspeaking of "things Apple leaks unintentionally", I found this one recently: https://github.com/apple-opensource/bless/blob/master/test/test_bless2
#asahi-re · 2022-06-17 04:42
marcan* ^ reused one register number, I meant
#asahi-re · 2022-06-17 04:41
marcanSo anything that we find in public sources also needs to be confirmed to be real, and often the bit assignments can change (e.g. AArch32 bits are unimplemented in M1 and newer chips) and that should be documented too.
#asahi-re · 2022-06-17 04:40
marcansometimes there are collisions too, so you need to be mindful to not just blindly copy. e.g. Apple reused one register name for two things, and Corellium had the wrong one in the mindless chicken bit sequence copy and paste they shipped in their port. We don't want that kind of nonsense.
#asahi-re · 2022-06-17 04:39
marcan... keys which is hinted to in XNU source, etc.)
#asahi-re · 2022-06-17 04:39
marcanprofessortox[m]: the register names in the wiki, to my knowledge, all came from collating references in various XNU source dumps and possibly some other public debug tools, and also guesswork (it's possible to come up with identical names to the original registers if you have related ones already, e.g. _EL12 variants are obvious, things like KNOWN_FEATURE_NAME_CFG, stuff related to pointer auth ...
#asahi-re · 2022-06-17 04:35
marcanAlso, I only use schematics that are widely available, i.e. I managed to dig up in a web search and they can be considered effectively public. I don't want anyone bringing in anything "they got from someone", that kind of stuff is a big liability risk (and that kind of culture is also toxic to open projects).
#asahi-re · 2022-06-17 04:32
marcan... schematics fundamentally contain.
#asahi-re · 2022-06-17 04:32
marcanAs for schematics: so far I've used those to come up with the GPIO backlight toggle stop-gap solution - which is why it isn't available on the iMacs, no schematics for those and I haven't bothered to brute force it - and to guess a lot of SMC hardware sensor keys. That kind of stuff is, as far as the end product, safe from copyright claims, since it is just factual information, which is what ...
#asahi-re · 2022-06-17 04:28
marcanBut that's the one exception. *Definitely* no leaked images, AppleInternal tools, stuff from prototype devices that "someone forgot in a bar", etc.
#asahi-re · 2022-06-17 04:27
marcanI make *one* exception to that second rule, leaked schematics, because there's practically no way for copyrightable content to wind up in our code from that and schematics should be available anyway for repairability purposes, and an entire industry depends on them.
#asahi-re · 2022-06-17 04:26
marcanStuff stolen or leaked from Apple internal channels is a no-no
#asahi-re · 2022-06-17 04:26
marcanThat includes things part of public betas, user-accessible field test images, and things like that
#asahi-re · 2022-06-17 04:26
marcanIn other words, stuff Apple publishes through open channels, intentionally or not, is considered equivalent for reverse engineering purposes and subject to the RE policy (which largely says you can't use it if it's copyrightable, see the RE policy for details)
#asahi-re · 2022-06-17 04:24
marcanAnd to be clear, "leaked" means specifically "not via official channels".
#asahi-re · 2022-06-16 19:05
professortox[m]Got it. Thank you
#asahi-re · 2022-06-16 14:13
alyssamade available to the public at large may be used. This applies to materials from both Apple and any other third parties.
#asahi-re · 2022-06-16 14:13
alyssaprofessortox[m]: Asahi Linux absolutely forbids the usage of any copyrighted materials not available to the public during reverse engineering. This includes any leaked software (in source or binary form), unreleased documentation, non-public releases (such as restricted betas), etc. Project contributors are expected to refrain from acquiring or using any such content. Only materials that are explicitly
#asahi-re · 2022-06-16 06:15
chadmedin fact the RE policy specifically says this
#asahi-re · 2022-06-16 06:06
chadmedthe legal problem with these is that in most cases, merely having the software at all is the illegal part
#asahi-re · 2022-06-16 06:05
chadmedrule of thumb is apple internal stuff = no no
#asahi-re · 2022-06-16 05:50
professortox[m]I got it from someone on twitter. Like I said, many of the existing registers (with the same numbers) in the wiki/XNU are almost the same in naming scheme. That's also what I was kind of curious about too since it isn't public.
#asahi-re · 2022-06-16 05:47
chadmedbeing AppleInternal you shouldnt use any reg names that cant be corroborated with publicly available sources
#asahi-re · 2022-06-16 05:45
chadmedhow did you get HomeDiagnostic?
#asahi-re · 2022-06-16 05:44
professortox[m]I only found some of them in XNU source. I don't think this list is even complete, but I have ~1k registers for Avalanche, some may be duplicate. All I really have are the names + the corresponding register number, which I decoded to sx_x_cx_cx_x format, but there is extra data that I'm not sure what it corresponds to. For now, I guess I'll just change the "unknow" register names and not add anything.
#asahi-re · 2022-06-16 05:32
chadmedimo you should be fine even with ones that arent since theyre just register names and youre not copying any of the actual code that can be considered IP (control flow and algorithms)
#asahi-re · 2022-06-16 05:32
chadmedif theyre in the XNU source then theyre fair game regardless since apple freely publish that
#asahi-re · 2022-06-16 05:31
professortox[m]A database file I found in HomeDiagnostic internal software for macOS. It has basic register definitions for most current Apple cpu cores going back to . I read the RE policy to not copy exactly, but I just want to be sure. Most of the registers I looked at that I found in XNU source are the same as what I have, minus the "ARM64_REG_" prefix
#asahi-re · 2022-06-16 05:20
chadmedhow did you get them? register names arent by themselves copyrightable material afaik so unless youre under NDA to not publish them then you should be okay
#asahi-re · 2022-06-16 05:17
professortox[m]Hi, I saw the System Registers Dump page in the GitHub wiki and I am interested in contributing to it (names for registers marked "unknow"). I've read the Copyright & Reverse Engineering page, but I'm unsure exactly how to proceed—should I post what I have and get permission here first?
#asahi-re · 2022-06-15 15:15
zx2c4lsr $50 you meant i think
#asahi-re · 2022-06-15 15:00
zx2c4_jannau_: not quite but i think i can reorder...
#asahi-re · 2022-06-15 14:49
sven(https://gitlab.arm.com/linux-arm/linux-rm/-/tree/iommu/bus)
#asahi-re · 2022-06-15 14:49
svenfwiw, i'll pick that 4k iommu back up once robin has finished his iommu api refactoring series. some of the changes become more sane once we already know the iommu instance by the time domain_alloc is called
#asahi-re · 2022-06-15 14:43
dougall(reminds me of copying decompiled code out of hex-rays and recompiling it with -Oz to make space for binary patches, not that i recommend that)
#asahi-re · 2022-06-15 14:40
_jannau_zx2c4: do you have by any chance a register which is guaranteed to have the top 14 bits set? `add x1, x1, xY, lsr #49`
#asahi-re · 2022-06-15 14:27
zx2c4hmm how do i turn a `add x1, x1, 4095` into a `add x1, x1, 16383` without needing an extra 4 bytes of .text
#asahi-re · 2022-06-15 14:13
zx2c4ahh, thanks
#asahi-re · 2022-06-15 14:13
_jannau_zx2c4: no immediate plans. the iommus use a page size of 16k and there is some effort needed to support that with smaller CPU page size. there is wip tree to so some of the work to support that: https://github.com/AsahiLinux/linux/tree/iommu-4k/dev
#asahi-re · 2022-06-15 14:09
AdryzzOLEDEdition[m]1there should be a 4k patch though
#asahi-re · 2022-06-15 14:09
AdryzzOLEDEdition[m]1no, the kernel will be kept at 16k so that people start fixing their software. and also, it is faster on 16k
#asahi-re · 2022-06-15 13:49
zx2c4marcan: any plans to switch the kernel to 4k pages?

plus ›