#asahi-re · 2024-04-07 20:52
svenit’s just the first layer which happens to be fairly simple. still lots of work to be done #asahi-re · 2024-04-07 20:42
ilmoThats awesome that there is a tracer for it already#asahi-re · 2024-04-07 20:42
ilmobut we can already see the communication in the hypervisor right?#asahi-re · 2024-04-07 20:35
svenvery likely even the same data the Bluetooth keyboards with touchid will send/receive #asahi-re · 2024-04-07 20:34
svenI’d expect that it’s essentially just passing encrypted data between the sensor and sep #asahi-re · 2024-04-07 20:34
svenTouch ID enrollment will already require the sep #asahi-re · 2024-04-07 20:33
svenand some code to boot the sep #asahi-re · 2024-04-07 20:33
sventhere’s a tracer in m1n1 that should decode the first layer ipc#asahi-re · 2024-04-07 20:32
svendunno if amarioguy made any progress #asahi-re · 2024-04-07 20:32
svenI did a bit of work a long time ago#asahi-re · 2024-04-07 20:32
ilmowould love to get in touch with anyone that worked on the sep tho#asahi-re · 2024-04-07 20:31
ilmoyeah the sep is necessary for touch id but I think just starting to look at how the touch id enrollment process works will also give a good starting point for the sep#asahi-re · 2024-04-07 20:27
jannauhaven't heard any for a while, svem might know more#asahi-re · 2024-04-07 20:25
jannauamarioguy was looking into sep (which you will need for touch id) and/or touch id#asahi-re · 2024-04-07 20:24
ilmoYea I'd be supried if it is the version but It's hard to explain this otherwise#asahi-re · 2024-04-07 20:23
jannauI would be surprised if it's the version and I think I usually do bputil, csrutil and kmutil in one go. glad it worked now#asahi-re · 2024-04-07 20:22
ilmoI'll be trying to re touch id now#asahi-re · 2024-04-07 20:21
ilmoThank you very much for your help!#asahi-re · 2024-04-07 20:21
ilmoOr maybe one thing that I did differently this time is after doing bputil and csrutil I rebooted, logged in, then reboot again into recovery, then set the boot object, reason I think this could be important is that it says reboot to apply SIP removal#asahi-re · 2024-04-07 20:19
ilmoAnd it worked!!!! Finally, so it was the version#asahi-re · 2024-04-07 20:19
ilmoYeah its not, now I'm restarting#asahi-re · 2024-04-07 20:19
jannauI don't think this is the error though#asahi-re · 2024-04-07 20:19
ilmoYeah, did thatn, now its the usual by setting a custom boot object you will be putting your system into permissive mode#asahi-re · 2024-04-07 20:18
jannauah. so shutdown and hold power until your booted into 1tr#asahi-re · 2024-04-07 20:18
ilmobefore when doing installations with 14.4 or other versions this did not appear, not that I think this has anything to do with the version but just never seen this happen till now#asahi-re · 2024-04-07 20:17
ilmoSo right now I have installed macOS 13.6.5, downloaded the KDK, did bputil,csrutil then I have executed the kmutil command and for the first time I have seen it complain about restarting and going into recovery again#asahi-re · 2024-04-07 20:15
jannauI can't follow#asahi-re · 2024-04-07 20:15
ilmoThis never appeared tho#asahi-re · 2024-04-07 20:15
ilmothe message about trying again after executing kmutil#asahi-re · 2024-04-07 20:14
jannauwhat appeared?#asahi-re · 2024-04-07 20:14
ilmoI compiled m1n1 on darwin, and used the m1n1 bin from the build directory#asahi-re · 2024-04-07 20:14
ilmoYes I was till now, actually now at this exact moment this appeared for me for the first time#asahi-re · 2024-04-07 20:13
jannauhow do you compile m1n1? are you using m1n1.bin with kmutil command line from https://github.com/AsahiLinux/docs/wiki/SW%3AHypervisor/#preparing-the-macos-volume-by-disabling-security-features ?#asahi-re · 2024-04-07 20:13
jannauyou're booting into 1tr by holding power until "loading boot options" appears? The tools should complain if not#asahi-re · 2024-04-07 20:12
ilmoI am sure I have selected the correct UUID by looking it up trough disk util#asahi-re · 2024-04-07 20:11
ilmojannau: Yes#asahi-re · 2024-04-07 20:10
jannauare you installing a second macOS volume?#asahi-re · 2024-04-07 20:08
ilmojannau: yeah I do think that it is me doing something wrong, but I've tried this many times already, I don't have any ideaabout why this could be happening, I installed macOS, bputil, csrutil, kmutil, then reboot into the macOS version I installed and it shows a white apple logo bootlooping#asahi-re · 2024-04-07 17:00
jannauI'd say it's more likely that you did something wrong or your m1n1 binary is broken than 14.5 not working, sorry. but it's still useful to RE work with a similar macOS version as everyone else#asahi-re · 2024-04-07 16:02
ilmoI'm just scared of another 1h 30mins download which won't work again, re wise it'll be fine for sure, just worrying about the m1n1 boot object not booting#asahi-re · 2024-04-07 15:56
jannaudepends on what you want to look at. if 13.6.6 is the closest still available version then it's probably similar enough (compared to 13.5)#asahi-re · 2024-04-07 15:51
ilmoUnfortunatley 13.5 is not avaliable anymore, will 13.6.6 work? or even 14.x? is there a list of known working versions?#asahi-re · 2024-04-07 15:45
jannau13.5(.0) but just check if the kdk is available before. not sure if it's still available via softwareupdate. exact version shouldn't matter that much for RE though#asahi-re · 2024-04-07 15:42
ilmoor should I get the correct one when using softwareupdate?#asahi-re · 2024-04-07 15:42
ilmojannau: which 13.5 build exactly? just so that I don't have the KDK problem again#asahi-re · 2024-04-07 15:42
jannauno it just makes not much sense to work with 12.3. HW obviously doesn't change over OS versions but 13.5 should be the starting point for firmware interfaces#asahi-re · 2024-04-07 15:39
ilmowill it make a big difference reverse engineering on 13.5 vs 12.3?#asahi-re · 2024-04-07 15:38
jannauyes, only m1n1 is loaded and it will wait for a connection via serial or usb#asahi-re · 2024-04-07 15:37
jannauuse 13.5, I'm asking because the instructions work over all m1/m2 devices (and select m3) up to 14.4#asahi-re · 2024-04-07 15:34
ilmoI mean m1n1 is loaded before macOS from what I understand, the serial communication is implemented in there, so shouldn't I see something happen in dmesg?