• 3 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: December 26th, 2023

help-circle

  • Not to sound stupid, but it really depends on how smart you want the watch to be. From connectionless firmware device to fully-featured Android. +1 for gadget bridge either way.

    I have a Fossil Hybrid, that combines physical hands with a 2-color e-ink display. It can’t do apps, but it has standalone timers, notifications, media control, pulse/oxygen and step counter. I personally don’t need more. It’s cloudless and lasts a week.

    If you need full Android/WearOS check AsteroidOS and specific ROMs. Hardware tends to be on the older side here.

    The only thing that’s hard to do is sleep tracking. That tends to rely on proprietary algorithms and cloud compute a lot.


  • Nicro@discuss.tchncs.detoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    23
    arrow-down
    6
    ·
    7 months ago

    Well the idea of having attestation isn’t the problem. The problem is that apps requiring attestation (banks, insurance providers, ID-systems) use the most convenient solution. Slapping on Googles prebuild attestation. Graphene for example, provides alternative attestation for their OS and offers docs for anyone to implement a more fitting set of checks.

    There are two approaches here: If you’re upset that your hacked-to-bits, rooted, unlocked and/or unencrypted device is failing checks: I’d say, tough luck. Until we can create provably untampered app-containers, that level of access genuinely breaks TOS on apps and regulations on handling personal data. Breaking those checks is then breaking those compliances in an unsafe way.

    If you believe your setup is actually secure and compliant, just not in a way the allmighty Google intended: Try and get an attestation module for your setup. Fight for these apps to accept non-Google attestation and fight for devices that don’t artificially limit what can pass as secure.


  • I feel there are plenty of local activist/independent servers all over the EU. As long as you mind the encryption/anonymization, you can even round-robin them. Having a central EU authority is better than Google/Cloudflare and should be safe, if the implementation is sound. But there is a lot of room to meddle.



  • Hey there, for starters A-GPS, stun, secure DNS, and several other preconfigured servers default to Google. Some of these can be changed with ADB. Check out a guide on de-googleing LineageOS for a more complete list. It’s not AOSP, but close enough. There are also Google servers configured in the sources. How valuable those connections are, depends on your threat-model. If you’d like a paranoid GSI, check out LeOS. It’s probably the most complete treble-compatible option. AOSP by default, isn’t very private.








  • Like others said, banking needs licensing and licensing costs money. If you already have a bank account, you already trust one party. Ask them if they roll their own app-payment or are already partnered with a service. That way, you can avoid google/Apple and minimize spreading the trust to other parties. My bank cooperates with Fidesmo, for example. Fidesmo then sells wearables with nfc-pay.