Open Link9875 opened 1 year ago
The issues with IOMMU and SMMU have been resolved. I'm unsure if there are any other security concerns within the Android system that need addressing, and I would appreciate some assistance in this matter. 🥲🥲
Nice to hear that you managed to get around / configure the SMMU to allow PCILeech.
I haven't looked into attacking Android / ChromeOS or similar so I can't really say what you could expect in this area. I always assumed it would be a bit harder than on PC and since this has been mostly a hobby project of mine I haven't found the time or will to look more closely into Android since I have a normal day job to take care of as well and the projects are quite large already...
Super interesting research though, please let me know if you should find out anything interesting around this 👍
Hello, I noticed that you've been trying to dump memory on Android devices and have come across the issue with IOMMU and SMMU that you mentioned Do you have any contact information so we can discuss this further? @Link9875
您好,我注意到您一直在尝试在 Android 设备上转储内存,并遇到了您提到的 IOMMU 和 SMMU 问题您是否有任何联系信息,以便我们进一步讨论? Thank you for your kindness, but I have already solved this problem perfectly. ^^
您好,我注意到您一直在尝试在 Android 设备上转储内存,并遇到了您提到的 IOMMU 和 SMMU 问题您是否有任何联系信息,以便我们进一步讨论? Thank you for your kindness, but I have already solved this problem perfectly. ^^
中国人?带一下哥哥
I'm using an ARM64 development board that's been loaded with Android 12. The kernel version includes solutions for both IOMMU and SMMU. However, I'm still encountering errors, and I'm not sure why.
Logger File is Created... Neko DHATEST Tool V5.0.0 Check at this path: ROOT_PATH INFO ] -> Retrieve connected device PCIe ID [4,0,12,0,000] ERROR: Unable to connect to memory acquisition device. Fail:13 [ INFO ] ->