Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K

KindnessInfinity

@ KindnessInfinity @lemmy.ml

Posts
816
Comments
188
Joined
3 yr. ago

She/Her

Spreading positivity and kindness

  • AOSP To Backport Critical Security Issues Reported By GrapheneOS Organization

    Jump

  • Yeah!

  • GrapheneOS Organization Discusses Wise Payment Problem

    Jump

  • Official introduction to Pixel 6 and Pixel 6 Pro on October 19 10am PT

    Jump

  • I wish I had Pixel 6 Pro back ehen it came out. I only had the 6.

  • GrapheneOS Organization Discusses Upstream Chromium Breakages and Asks For Help With App Testing From Community

    Jump

  • What version of vanadium are you using?

  • GrapheneOS Organization Discusses Upstream Chromium Breakages and Asks For Help With App Testing From Community

    Jump

  • When you use it. What is the expected behavior? Are you expecting it to autofill the password and username when you visit a login page?

  • GrapheneOS Organization Discusses Upstream Chromium Breakages and Asks For Help With App Testing From Community

    Jump

  • What is not working? This is very vague

  • GrapheneOS Organization Discusses Upstream Chromium Breakages and Asks For Help With App Testing From Community

    Jump

  • May you please explain what the issue was?

  • Deleted

    Permanently Deleted

    Jump

  • Clearly a woman. "My lady" would've been more appropriate. Please don't be rude

  • GmsCompatConfig (sandboxed Google Play compatibility layer configuration) version 117 released

    Jump

  • Haha 😂

  • ‘You’re Telling Me in 2023, You Still Have a ’Droid?’ Why Teens Hate Android Phones

    Jump

  • Good one! :)

  • GrapheneOS Now Supports a Duress Reset PIN and More

    Jump

  • Also, could you have a duress pin+fingerprint in addition to a duress password?

    They are planning to have a second unlock method for After First Unlock in the future.

  • GrapheneOS Now Supports a Duress Reset PIN and More

    Jump

  • That is correct. During setup, you're prompted for both password and pin which allows use with pin or password prompts

  • GrapheneOS Now Supports a Duress Reset PIN and More

    Jump

  • Last time I checked, that app uses accessibility services, which are not recommended by the GOS project. As accessibility services greatly increases attack surface if any app using these services are compromised.

  • GrapheneOS Now Supports a Duress Reset PIN and More

    Jump

  • GrapheneOS Organization Discusses Issues With Upstream Linux Kernel

    Jump

  • This would be:

    In the long term, GrapheneOS aims to move beyond a hardened fork of the Android Open Source Project. Achieving the goals requires moving away from relying on the Linux kernel as the core of the OS and foundation of the security model. It needs to move towards a microkernel-based model with a Linux compatibility layer, with many stepping stones leading towards that goal including adopting virtualization-based isolation.

    The initial phase for the long-term roadmap of moving away from the current foundation will be to deploy and integrate a hypervisor like Xen to leverage it for reinforcing existing security boundaries. Linux would be running inside the virtual machines at this point, inside and outside of the sandboxes being reinforced. In the longer term, Linux inside the sandboxes can be replaced with a compatibility layer like gVisor, which would need to be ported to arm64 and given a new backend alongside the existing KVM backend. Over the longer term, i.e. many years from now, Linux can fade away completely and so can the usage of virtualization. The anticipation is that many other projects are going to be interested in this kind of migration, so it's not going to be solely a GrapheneOS project, as demonstrated by the current existence of the gVisor project and various other projects working on virtualization deployments for mobile. Having a hypervisor with verified boot still intact will also provide a way to achieve some of the goals based on extensions to Trusted Execution Environment (TEE) functionality even without having GrapheneOS hardware.

    Hardware and firmware security are core parts of the project, but it's currently limited to research and submitting suggestions and bug reports upstream. In the long term, the project will need to move into the hardware space.

    source

  • GtapheneOS Discusses How Chromium Releases Are Handled and How They Impact Security

    Jump

  • Vanadium is still more secure than fennec

    Why? Well, vanadium has these security improvements:

    • Type-based Control Flow Integrity (CFI)
    • Hardware memory tagging (MTE) enabled for the main allocator
    • Strict site isolation and sandboxed iframes
    • JavaScript JIT disabled by default with per-site toggle via drop-down permission menu

    Also many more security improvements

  • GrapheneOS News About Latest OS Release and VPN DNS Bugs

    Jump

  • GrapheneOS version 2024042000 released

    Jump

  • Thank you. Me too

  • GrapheneOS Organization Discusses Developments With Their Reported Vulnerabilities In AOSP and Future Duress Reset Features

    Jump

  • The physical USB data lines are disabled by the OS's current USB management, this is done as USB device ID's can be spoofed, which opens up a security whole.