#asahi-dev · 2026-01-22 07:37
svenIf that happens we can discuss moving somewhere else imho #asahi-dev · 2026-01-22 07:37
sveninside asahilinux?#asahi-dev · 2026-01-22 07:37
svenbut have you seen it on any PR? #asahi-dev · 2026-01-20 17:28
svennickchan: or just move the endpoint decision into the drivers for now#asahi-dev · 2026-01-20 17:28
svenSEP will ask you to update that file via the xars/xarm endpoints and you kinda have to do that#asahi-dev · 2026-01-20 17:27
sveniirc i deleted that xart file just to see what happens and ended up in dfu :D#asahi-dev · 2026-01-20 17:26
svenplease read https://asahilinux.org/copyright/ and especially the reverse engineering policy#asahi-dev · 2026-01-20 17:25
svenhttps://f.svpe.de/262f757f4eef4825164bd703903e9f5ef2f76bd6ca410511a101a361b62084ed_gl_parse.py.txt i guess those were my notes before i gave up due to the risk of dfu trips#asahi-dev · 2026-01-20 17:23
sveni have some notes on the gigalocker format itself somewhere, but it's just a simple key/value store#asahi-dev · 2026-01-20 17:23
sveni wouldn't make assumptions at this stage tbh#asahi-dev · 2026-01-20 17:22
sventheir security architecture is good enough, they don't need to rely on obscurity #asahi-dev · 2026-01-20 17:22
svenso?#asahi-dev · 2026-01-20 17:21
svenmaybe, xnu can be very verbose at times#asahi-dev · 2026-01-20 17:21
svenyeah#asahi-dev · 2026-01-20 17:20
svenunfortunately the sensor won't talk to us at all and e.g. give us raw fingerprint data so we can't just bypass SEP #asahi-dev · 2026-01-20 17:20
sventouchid is a surprisingly big project ;)#asahi-dev · 2026-01-20 17:19
svenno idea :D#asahi-dev · 2026-01-20 17:18
svenyeah, but i'm sure there's also lots of unrelated stuff happening. no one really looked into this so far :-)#asahi-dev · 2026-01-20 17:17
sventhere's certainly stuff happening on boot, but no one knows what exactly and what's actually required#asahi-dev · 2026-01-20 17:17
svenno idea#asahi-dev · 2026-01-20 17:17
svenstage?#asahi-dev · 2026-01-20 17:16
sveni kinda expect the first part of easily take 80% of the work#asahi-dev · 2026-01-20 17:16
sventouchid is then just shuffling encrypted data between SEP and the touchid hardware#asahi-dev · 2026-01-20 17:15
svenyou first need SEP to talk to you and understand how the user management there works#asahi-dev · 2026-01-20 17:15
sventhat will come much later#asahi-dev · 2026-01-20 17:15
svenhttps://github.com/AsahiLinux/m1n1/blob/main/proxyclient/m1n1/hw/sep.py no idea if it still works :-)#asahi-dev · 2026-01-20 17:14
sveniirc there's some initial SEP tracer in there already#asahi-dev · 2026-01-20 17:14
svenyeah#asahi-dev · 2026-01-20 17:14
sventhen once that works we can think about the linux driver and userspace daemon should look like#asahi-dev · 2026-01-20 17:14
sventhen try to build some python script that talks to SEP. for touchid you need at least user management and the communication with that touchid peripheral#asahi-dev · 2026-01-20 17:13
sventhat's likely also gonna be faster than reversing the kext (and probably also userspace)#asahi-dev · 2026-01-20 17:13
svenhook the SEP communication and stare at the protocol to figure it out#asahi-dev · 2026-01-20 17:12
svenno, we try to avoid binary reverse engineering whenever possible#asahi-dev · 2026-01-20 17:11
svenand this kinda needs a dedicated machine because if you mess that xART locker file up you might need to DFU revive the mac#asahi-dev · 2026-01-20 17:11
svenwhat needs to be done is reverse engineering of the SEP<->AP protocol#asahi-dev · 2026-01-20 17:10
svenreally, ignore APFS#asahi-dev · 2026-01-20 17:10
svendon't bother with APFS#asahi-dev · 2026-01-20 17:10
svenjust find the start offset and take it from there#asahi-dev · 2026-01-20 17:10
svenapfs isn't the issue, the file is continuous on the disk#asahi-dev · 2026-01-20 17:09
sventhis is gonna need significant SEP reversing fwiw #asahi-dev · 2026-01-20 15:04
svenm4, should be t8132 I think #asahi-dev · 2026-01-19 20:45
sven*then#asahi-dev · 2026-01-19 20:45
sventhe once I fix the atcphy issue those will just work as well on Linux #asahi-dev · 2026-01-19 20:44
svenok nice #asahi-dev · 2026-01-19 20:23
sventhose were my bootargs in that old log#asahi-dev · 2026-01-19 20:23
svenAppleTypeCPhyInterface-debug=0xffff AppleTypeCPhyUSBInterface-debug=0xffff AppleUSBHostResourcesTypeC-debug=0xffff tbdebug=0xffff tblog=1#asahi-dev · 2026-01-19 20:23
sven<Notice>: boot-args = debug=0x14e serial=3 apcie=0xfffffffe wdt=-1 AppleSynopsysDRDUSBXHCI-debug=0xffff AppleT8103TypeCPhy-debug=0xffff AppleT8103USB40XHCITypeCPort-debug=0xffff AppleT8103USBXDCI-debug=0xffff AppleTypeCPhy-debug=0xffff AppleTypeCPhyCIOInterface-debug=0xffff AppleTypeCPhyDisplayPortInterface-debug=0xffffffff#asahi-dev · 2026-01-19 20:21
svenmaybe they removed that print in later macos versions :/#asahi-dev · 2026-01-19 20:21
sventhat's strange#asahi-dev · 2026-01-19 20:18
svenand that changes depending on the cable type