#
…

2024-04-07

00:12pb17 has joined #asahi-re
01:00KxCORP5 has quit [Quit: Bye!]
01:01KxCORP5 has joined #asahi-re
02:02KxCORP5 has quit [Quit: Bye!]
02:02KxCORP5 has joined #asahi-re
02:14pb17 has quit [Ping timeout: 480 seconds]
02:21pb17 has joined #asahi-re
02:27hdbngr has joined #asahi-re
02:36hdbngr has quit [Ping timeout: 480 seconds]
03:35jeisom has quit [Ping timeout: 480 seconds]
03:59hdbngr has joined #asahi-re
04:09hdbngr has quit [Ping timeout: 480 seconds]
04:25annan_person_ has joined #asahi-re
04:30annan_person has quit [Ping timeout: 480 seconds]
04:30annan_person_ is now known as annan_person
05:00midou has quit [Ping timeout: 480 seconds]
05:07foxtrot has quit [Quit: Goodbye]
05:25pb17 has quit [Ping timeout: 480 seconds]
05:49pb17 has joined #asahi-re
06:02hdbngr has joined #asahi-re
06:03foxtrot has joined #asahi-re
06:10hdbngr has quit [Ping timeout: 480 seconds]
06:11nicolas17 has quit [Remote host closed the connection]
06:13hdbngr has joined #asahi-re
06:19midou has joined #asahi-re
06:22hdbngr has quit [Ping timeout: 480 seconds]
06:51nela has quit [Quit: bye!]
06:52nela has joined #asahi-re
07:03hdbngr has joined #asahi-re
07:11hdbngr has quit [Ping timeout: 480 seconds]
07:33hdbngr has joined #asahi-re
07:41midou has quit [Ping timeout: 480 seconds]
07:45hdbngr has quit [Ping timeout: 480 seconds]
08:04hdbngr has joined #asahi-re
08:12hdbngr has quit [Ping timeout: 480 seconds]
08:27pb17 has quit [Ping timeout: 480 seconds]
08:35midou has joined #asahi-re
08:38pb17 has joined #asahi-re
09:05hdbngr has joined #asahi-re
09:09JayBeeFOSS has quit [Ping timeout: 480 seconds]
09:10JayBeeFOSS has joined #asahi-re
09:13hdbngr has quit [Ping timeout: 480 seconds]
09:33schroes has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
09:48schroes has joined #asahi-re
10:06hdbngr has joined #asahi-re
10:14hdbngr has quit [Ping timeout: 480 seconds]
10:24pb17 has quit [Ping timeout: 480 seconds]
10:40hdbngr has joined #asahi-re
10:49hdbngr has quit [Ping timeout: 480 seconds]
11:04pb17 has joined #asahi-re
11:07hdbngr has joined #asahi-re
11:15hdbngr has quit [Ping timeout: 480 seconds]
12:08hdbngr has joined #asahi-re
12:16hdbngr has quit [Ping timeout: 480 seconds]
12:17hdbngr has joined #asahi-re
12:22jeisom has joined #asahi-re
12:26hdbngr has quit [Ping timeout: 480 seconds]
12:40eloy__ has quit []
12:40eloy_ has joined #asahi-re
12:41jeisom has quit [Remote host closed the connection]
12:42jeisom has joined #asahi-re
12:48pb17 has quit [Ping timeout: 480 seconds]
12:50pb17 has joined #asahi-re
13:09hdbngr has joined #asahi-re
13:17hdbngr has quit [Ping timeout: 480 seconds]
14:00pb17 has quit [Ping timeout: 480 seconds]
14:05hdbngr has joined #asahi-re
14:15hdbngr has quit [Ping timeout: 480 seconds]
14:16pb17 has joined #asahi-re
14:19hdbngr has joined #asahi-re
14:28hdbngr has quit [Ping timeout: 480 seconds]
14:28SalimTer- has joined #asahi-re
14:33SalimTerryLi has quit [Ping timeout: 480 seconds]
15:04ilm has joined #asahi-re
15:04ilm has left #asahi-re [#asahi-re]
15:07ilmo has joined #asahi-re
15:09ilmohi, I have installed macOS 14.5 build 23F5049f, gone trough the m1n1 hypervisor setup in the recovery, set the m1n1 custom boot object and now macOS is stuck in an infinite boot loop which eventually results in being thrown into recovery and I do not see any serial tty device getting attached, dmesg is empty
15:25jannauilmo: on which device? in which partition did you install m1n1 as custom boot object? the 14.5 macOS one?
15:28ilmoYes, the 14.5 one for sure, device is the m1 pro macbook pro
15:30ilmojannau: I am also connecting using a usb 2.0 cable, it has data lines
15:30ilmoUSB A to USB C
15:31jannaudid this work before with a different macOS version? did set the boot policy / disable sip like in https://github.com/AsahiLinux/docs/wiki/SW%3AHypervisor/#preparing-the-macos-volume-by-disabling-security-features
15:34ilmojannau: Yes, I have set up the bootpolicy and sip according to the instructions there, I have also not tried this with any other macOS version yet as I always had it install versions which did not have a KDK, now I am downloading 12.3, but would this macOS version make a difference?
15:34ilmoI 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?
15:37jannauuse 13.5, I'm asking because the instructions work over all m1/m2 devices (and select m3) up to 14.4
15:38jannauyes, only m1n1 is loaded and it will wait for a connection via serial or usb
15:39ilmowill it make a big difference reverse engineering on 13.5 vs 12.3?
15:42jannauno 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
15:42ilmojannau: which 13.5 build exactly? just so that I don't have the KDK problem again
15:42ilmoor should I get the correct one when using softwareupdate?
15:45jannau13.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
15:46HardWall has joined #asahi-re
15:51ilmoUnfortunatley 13.5 is not avaliable anymore, will 13.6.6 work? or even 14.x? is there a list of known working versions?
15:56jannaudepends 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)
16:02ilmoI'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
16:08hdbngr has joined #asahi-re
16:19hdbngr has quit [Ping timeout: 480 seconds]
16:23pb17 has quit [Ping timeout: 480 seconds]
16:29ilmo_ has joined #asahi-re
16:57pb17 has joined #asahi-re
17:00jannauI'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
17:12hdbngr has joined #asahi-re
17:20hdbngr has quit [Ping timeout: 480 seconds]
17:25hdbngr has joined #asahi-re
17:33hdbngr has quit [Ping timeout: 480 seconds]
17:47hdbngr has joined #asahi-re
17:55hdbngr has quit [Ping timeout: 480 seconds]
18:01glem has quit [Quit: bye.]
18:13hdbngr has joined #asahi-re
18:13glem has joined #asahi-re
18:14pb17 has quit [Ping timeout: 480 seconds]
18:21pb17 has joined #asahi-re
18:21hdbngr has quit [Ping timeout: 480 seconds]
18:26hdbngr has joined #asahi-re
18:27jeisom has quit [Remote host closed the connection]
18:34hdbngr has quit [Ping timeout: 480 seconds]
18:43hdbngr has joined #asahi-re
18:51hdbngr has quit [Ping timeout: 480 seconds]
18:54hdbngr has joined #asahi-re
19:06hdbngr has quit [Ping timeout: 480 seconds]
19:26gi0 has quit []
19:40ilmo has quit [Remote host closed the connection]
19:56pb17 has quit [Ping timeout: 480 seconds]
20:00ilmo_ has quit [Quit: WeeChat 4.1.1]
20:05ilmo has joined #asahi-re
20:08ilmojannau: 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
20:10jannauare you installing a second macOS volume?
20:11ilmojannau: Yes
20:12ilmoI am sure I have selected the correct UUID by looking it up trough disk util
20:13jannauyou're booting into 1tr by holding power until "loading boot options" appears? The tools should complain if not
20:14ilmoYes I was till now, actually now at this exact moment this appeared for me for the first time
20:14ilmoI compiled m1n1 on darwin, and used the m1n1 bin from the build directory
20:14jannauwhat appeared?
20:15ilmothe message about trying again after executing kmutil
20:15ilmoThis never appeared tho
20:15hdbngr has joined #asahi-re
20:15jannauI can't follow
20:17ilmoSo 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
20:18ilmobefore 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
20:18jannauah. so shutdown and hold power until your booted into 1tr
20:19ilmoYeah, did thatn, now its the usual by setting a custom boot object you will be putting your system into permissive mode
20:19jannauI don't think this is the error though
20:19ilmoYeah its not, now I'm restarting
20:19ilmoAnd it worked!!!! Finally, so it was the version
20:21ilmoOr 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
20:21ilmoThank you very much for your help!
20:22ilmoI'll be trying to re touch id now
20:23jannauI 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
20:23hdbngr has quit [Ping timeout: 480 seconds]
20:24ilmoYea I'd be supried if it is the version but It's hard to explain this otherwise
20:25jannauamarioguy was looking into sep (which you will need for touch id) and/or touch id
20:27jannauhaven't heard any for a while, svem might know more
20:31ilmoyeah 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
20:32ilmowould love to get in touch with anyone that worked on the sep tho
20:32svenI did a bit of work a long time ago
20:32svendunno if amarioguy made any progress
20:33sventhere’s a tracer in m1n1 that should decode the first layer ipc
20:33svenand some code to boot the sep
20:34svenTouch ID enrollment will already require the sep
20:34svenI’d expect that it’s essentially just passing encrypted data between the sensor and sep
20:35pb17 has joined #asahi-re
20:35svenvery likely even the same data the Bluetooth keyboards with touchid will send/receive
20:42ilmobut we can already see the communication in the hypervisor right?
20:42ilmoThats awesome that there is a tracer for it already
20:42ilmo has quit [Quit: WeeChat 4.1.1]
20:44roxfan has quit [Remote host closed the connection]
20:45ilmo has joined #asahi-re
20:48roxfan has joined #asahi-re
20:52roxfan has quit [Remote host closed the connection]
20:52svenit’s just the first layer which happens to be fairly simple. still lots of work to be done
20:52svenand yeah, you should be able to see everything with the hv
20:55roxfan has joined #asahi-re
21:16hdbngr has joined #asahi-re
21:24hdbngr has quit [Ping timeout: 480 seconds]
22:00pb17 has quit [Ping timeout: 480 seconds]
22:05pb17 has joined #asahi-re
22:17hdbngr has joined #asahi-re
22:25hdbngr has quit [Ping timeout: 480 seconds]
22:29ilmo has quit [Quit: WeeChat 4.1.1]
23:11hdbngr has joined #asahi-re
23:21opticron has quit [Ping timeout: 480 seconds]
23:26hdbngr has quit [Ping timeout: 480 seconds]
…