• 11 Posts
  • 259 Comments
Joined 1 year ago
cake
Cake day: September 29th, 2023

help-circle


  • exu@feditown.comtolinuxmemes@lemmy.worldPrivacy meme
    link
    fedilink
    English
    arrow-up
    4
    ·
    4 days ago

    Yes, microG works without root, however to get it working as a network location provider you either need it installed as system app (for example LOS4microg) or patch android to allow non-system apps for providing network location.

    There’s an official patch, also mentioned in the Install Guide and it’s basically the reason for microg_installer and its revived fork existing.

    I could use LOS4microg, which does include the patch, but builds are run much less frequently (once a month instead of weekly) and I’d rather stick to original Lineage.

    Thanks for pointing out charging control, I wasn’t aware of that new feature. One more reason to upgrade LOS my phone


  • exu@feditown.comtolinuxmemes@lemmy.worldPrivacy meme
    link
    fedilink
    English
    arrow-up
    20
    ·
    4 days ago

    I also do that because it lets me

    • limit charging with ACC
    • use microG as network location provider (microg installer revived)
    • fix SafetyNet
    • YouTube ReVanced
    • Make using other App stores easier (updating can happen automatically in more recent Android versions, but first installs still require confirmation outside the Play Store)





  • The .mobi was a previous post where they bought the expired domain which was previously used by the .mobi WHOIS server.
    A bunch of systems apparently didn’t update their WHOIS database and still tried to get WHOIS information from the old domain.
    This could lead to RCE in some implementations if they provided a malicious response.
    A bunch of CAs also accessed the old domain and use WHOIS to verify domain ownership. By setting their own email address for verification, they could have issued themselves a certificate for any .mobi domain (microsoft.mobi, google.mobi for examle).

    Now to this article, here they looked at a bunch of webshells with backdoors added by the developers. Some of the domains had expired, so by getting those domains and setting up a webserver they got connections from different systems infected by the malware. They could have used the same backdoor previously used by the devs to access those same systems remotely and do whatever.