• 4 Posts
  • 469 Comments
Joined 11 months ago
cake
Cake day: June 6th, 2025

help-circle

  • Hm, I’m reading the spec. It seems more simplistic than I was expecting.

    Issuance of Proof of Age attestations (step 3)

    Once the User’s age has been verified, the AP may either issue the Proof of Age attestation directly to the User’s AVI or generate a pre-authorized code and provide it to the User as part of a credential offer. At a later stage, the User can present this credential offer through their AVI to obtain the Proof of Age attestation.

    Confirmation and presentation (step 5)

    The AVI receives the Proof of Age request and presents it to the User. The User reviews the request details, verifies the information, and confirms the transaction to proceed.

    The AVI securely transmits the Proof of Age attestation to the RP.

    Guess it does just pass the attestation around.

    2.2.3 Revocation and Re-Issuance In its current form, the solution does not support revocation or re-issuance. Adding support for these features would introduce additional complexity, which could hinder the rapid adoption of the solution.

    The attestation is ideally only used once and issued in batches, so this is both good and bad I guess, since if they ask to track you and they haven’t already recorded all the attestations, they’ll need to wait for you to generate more.

    Unlinkability: The goal of the solution is to prevent user profiling and tracking by avoiding linkable transactions. Initially, the solution will rely on batch issuance to protect users from colluding RPs. Zero-Knowledge Proof (ZKP) mechanisms will be considered to offer protection. More details are provided in Section 7.

    Basically a big TBD. Lovely.

    The more subtle attack you mention could probably be avoided if the root certs and so on or whatever equivalent they’re using are public and you check that the attestation given to you doesn’t include extraneous details (which ideally the app would do for you). Not sure how that’ll interact with the zkSNARK solution provided as an “experimental feature.”

    It doesn’t really matter though since they can just record the attestations when they’re issued, so they just have to say “look for these attestations” to whatever site and they can track your visits.

    It is recommended that the Proof of Age attestation be designed as a single-use credential and remain valid for a maximum period of three (3) months from the date of issuance. If a revocation mechanism is required, a status list may be utilized as an effective solution for managing the revocation status of attestations.

    Of course, using it in batches is only “recommended,” so I guess they could just issue it once and continuously reuse it, in which case it would be very easy for websites to link it to you.

    There’s probably more I could pull out, but yeah, doesn’t seem great based on the spec :|

    EDIT: based on my reading of the ZKP spec linked in the main spec, it seems like it should work correctly, but as long as it’s an “experimental feature” and not always used it’s not really useful. They mention that in cases where the ZKP setup can’t be used it should be able to fallback to the token setup. Ideally it really shouldn’t do that, especially if it doesn’t specifically tell you that it can’t continue without using ZKPs and thus potentially leaking your identity.



  • I realize this probably won’t change anything given what you’ve said, but I felt compelled to reply.

    I do not think banning something because it has queer representation or something similar is a good idea. I haven’t watched that show, so I cannot comment on it in particular, but if all it was doing was going “here are these queer people living normal lives like everyone else,” then there’s no real harm. All banning stuff like ylthat really does is cement in your child’s head that these people are weird and abnormal when she finds out they exist (especially if she asks your wife, it sounds like). Importantly, hiding stuff from your kids isn’t gonna stop them from learning about it, they’ll learn through alternate sources eventually.

    Anecdotally, my conservative parents did something similar with my younger brother. They banned certain children’s networks on TV when he was growing because they didn’t like the content. Well, he eventually got unfettered access to YouTube and the internet as a whole and is now a fascist (self-described). Presumably the only reason he isn’t virulently anti-LGBTQ+ is because I am LGBTQ+. I, on the other hand, had to research practically everything myself because I felt like I had no one I could talk to given my parents’ views (especially given some of the horror stories on the internet). Note that I grew up when LGBTQ+ representation in children’s shows was pretty much nonexistent or super minor still.





  • Generally there are no real problems. If you’re fine with mostly stock AOSP, you should be fine with GrapheneOS.

    If you use Google Pay, you’re out of luck. There are alternatives for that depending on where you live though (mostly in Europe, in the US there’s no other option AFAIK). Rarely an app won’t work, but usually fiddling with some security settings for the app will fix it. Very rarely an app won’t work at all because (like Google Wallet) it uses Play Integrity and requires a level that requires Google to certify the OS.

    Pretty much the only thing I miss is the ability to do NFC payments.