• 1 Post
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle


  • Their statement is that Alpine is designed to be friendly to corporations who want to lock down their devices and prevent you from modifying them.

    You cannot use coreutils and have a DRM locked down device.

    You can use Alpine w/ musl + busybox and make a DRM locked down device

    Alpine’s licensing favors large corporation’s rights in preventing the user from modifying their device

    Operating systems using coreutils favor the end user’s rights


  • If they can take my unlocked device by force, they can probably also break my fingers to coerce me to unlock it See also: https://xkcd.com/538/

    Randall is right in pointing out you need to consider your attack vectors, but this doesn’t mean you shouldn’t take reasonable precautions

    Most people are more likely to run into the type of attack OP references than someone who can break LUKS encryption stealing their device








  • That’s already how it functionally worked for each major release

    Here’s their previous strategy: https://web.archive.org/web/20220917195332/source.android.com/docs/setup/about/codelines

    Google works internally on the next version of the Android platform and framework according to the product’s needs and goals

    When the n+1th version is ready, it’s published to the public source tree

    The source management strategy above includes a codeline that Google keeps private to focus attention on the current public version of Android.

    We recognize that many contributors disagree with this approach and we respect their points of view. However, this is the approach we feel is best and the one we’ve chosen to implement for Android.

    As far as I can tell, this would really only affect QPRs, since the public experimental branches that get made after they throw the next release over the wall is going away





  • I think the bigger complaint is that, when Galaxy was released, GOG said (back in 2015)

    A Linux version of our client is planned eventually … Stay tuned for future announcements

    Ten years is plenty of time to implement a launcher, or at least give a planned timeline

    Sure, third parties have done it with Heroic, etc. but promising support and not delivering leaves a really bad taste to me


  • The article is a security company trying to hype their company with a theoretical attack that currently has no hypothetical way to be abused

    The article has an update now fixing the wording to “hidden feature” but, spoilers, every BT device has vendor specific commands.

    The documentation of the part just wasn’t complete and this companies “fuzzing” tool found some vendor commands that weren’t in the data sheet

    The China part just came from OP