Auditor app version 92 released

GrapheneOS

Auditor app version 92 released:

https://github.com/GrapheneOS/Auditor/releases/tag/92

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.

xxx

GrapheneOS
Working fine P6 & P9.

Kamika242

I don't understand what the Auditor is for. I tried to audit my Pixel via an Samsung Galaxy Tab A9+ and had some meaningless technical details on an orange background. No clue what this tells me.

xxx

Kamika242 don't understand what the Auditor is for. I tried to audit my Pixel

You can use remote attestation:
https://attestation.app/

Basically it tells you your installation hasn' t been tampered with. -> is the original rom.

GrapheneOS

Kamika242 The details shown on the page aren't meaningless and you can understand nearly all of it without technical knowledge. If it shows the device model, OS, OS version and patch level are what they should be then it's showing you that it verified the device is fine. It also shows useful supplementary info on OS configuration which you can make sure matches what it should be such as there being no accessibility service or device manager in most cases which could be hidden from you on the device itself. The point of it is obtaining verified info which a compromised device could hide from you. The hardware verified info can't be faked by an attacker successfully compromising the OS and the OS verified info can't be faked without currently having a deep system level compromise of the OS. The OS verified info is to protect against malware and also a past deep compromise of the OS which has degraded to persistence via stuff that can be done without an exploit of the OS each boot working fine. An attacker would generally need to hold back OS updates to keep successfully exploiting it at each boot.

Kamika242

xxx

Thank you. I created an account, selected "Enable remote verification" in the app on my phone, scanned the QR code, but the larger QR code for audition via another device appeared nevertheless, can I ignore this?
In the web app I set up my email address, did a refresh and details of my phone were shown, thats all and my device from now on will be audited regularly?

GrapheneOS

Kamika242 You accidentally pressed the Auditee mode button after it scanned the remote verification subscription code.

Kamika242

GrapheneOS You accidentally pressed the Auditee mode button after it scanned the remote verification subscription code.

No, there were 3 options in the menu, device is auditee, device is auditor and remote audition. Before clicking the third option I deleted all existing connections via the 3 dots menu.
From the large QR code meant for another device was no turning back, the back button/gesture everytime closed the app regularly, no other options were available anymore.
Now, a little later, I opened the Auditor app again, the large QR code disappeared and only the 2 options for audition of/by another device are available, finally my phone seems to be connected to the web audition service successfully. The 3 dots menu now shows an option "Disable remote verification".
The long way to here was very confusing.

GrapheneOS The details shown on the page aren't meaningless and you can understand nearly all of it without technical knowledge.

The details shown in the web auditor are fully understandable to me, the details shown in the auditor app of my tablet pc were cryptic and the orange background implicated a warning, while searching in the web I basically saw only green backgrounds.

Cheers and thanks!

Developer-Dude

Kamika242 and the orange background implicated a warning

You must verify the device twice on the very first time. The very first time will be orange. The second time and so on should be green. Verify it again.

GrapheneOS

Kamika242 It's the same information in both Auditor and the https://attestation.app/ service with the same wording. The local verification system doesn't have a user interface for managing pairings yet and can't show a history of past verifications yet.

Kamika242 That's because you started the process of pairing and didn't complete it. This can't happen with the remote verification service since it has 2-way communication over an HTTPS connection. For local verification, the Auditee doesn't know if you completed the process. We plan to provide a cancel button to delete the pairing if it wasn't completed but for now you must complete the initial pairing or clear Auditor pairings on the Auditor side if you don't. Alternatively, clear Auditee pairings on the Auditee side. Clearing Auditee pairings won't interfere with the remote verification which has a separate namespace for the pairing not deleted by clearing those, but you can just clear Auditor pairings on the Auditor side instead. In the future there will be a way to manage local pairings to delete specific ones.

Tablets have awful cameras and will struggle to read the QR code from the Auditee. It might help to hold it fairly far away and make sure there's a lot of light since those poor cameras are very bad in low light.

Kamika242

Developer-Dude

Just tried, but my Samsung tablets camera has enormous problems to read the large QR code. Will try again tomorrow at daylight.

Kamika242

Developer-Dude

Was able to verify again today, red background and the following text:

Error encountered verifying attestation:

Pairing data for this Auditee is missing. Cannot perform paired attestation.

Either the initial pairing was incomplete or the device is compromised.

If the initial pairing was simply not completed, clear the pairing data on either the Auditee or the Auditor via the menu and try again.

I'll leave it at that, because the remote attestation runs fine and displays no issues.

zenit

I understood the use of Auditor for verifying devices locally, but I was slow to recognize the utility of the remote verification service. Wish I'd set it up when I first started using GrapheneOS.

Developer-Dude

Kamika242 pair it once more again. If its red again, this could be a compromised device for some reason. Note, I'm not completely sure, so maybe others have ideas. @Johnnyloans knows his stuff, he may know.

Kamika242

Developer-Dude If its red again, this could be a compromised device for some reason.

But when remote attestation says "Everything is fine", but another device says "Device could be compromised", what should I believe?

Kamika242

Developer-Dude

Johnnyloans

GrapheneOS

Finally I got it to work. Deleted all previous pairings again on both devices (except remote connection), the first result had the orange background again, but an excellent rating, the second result had a green background and exactly the same rating as before and on remote.
Another good way to confuse users. 😂

GrapheneOS Tablets have awful cameras compared to phones and reading a dense QR code is difficult.

Indeed. 😥

Johnnyloans

Kamika242

I'd believe remote. Maybe a Samsung can't test a GrapheneOS phone correctly, not sure. I haven't tried that before.

GrapheneOS

Johnnyloans It works fine on Samsung devices. Tablets have awful cameras compared to phones and reading a dense QR code is difficult. Auditor local verification requires a decent camera on the Auditor side to read the dense QR code. It can be worked around by providing a lot of light in a way that doesn't create a reflection on the screen and trying to scan from a bit further away. There's not much we can do about devices having awful cameras with terrible focus which are unable to properly focus on the QR code. Holding it further away will help it focus.

rfm

When looking at the remote attestation results everything looks fine so far, however it says 3 users even though I only have owner and one daily driver. Is this to be expected (maybe guest account is counted in although it is not activated or something like that)?

Johnnyloans

rfm however it says 3 users

Each private space is another "user" as well.

I wouldn't go around saying that [issue] doesn't work in my other user when I really mean private space.
This just means that private space is completely separate from from the rest of the android system like the user accounts are separate.

GrapheneOS

rfm Work profiles and Private Spaces are users too. It could say profiles instead of users but we aren't sure that's easier to understand.