• 3 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle






  • It’s a question of security risk profiles.

    Security ultimately often times comes with a tradeoff for user experience or privacy.

    How does device integrity checks materially affect the security posture for theft when considering this system? Presumably the security checks for remotely unlocking a car is based around credentials and authN/authZ for the unlock service call?

    Enforcing client side security has entered the picture recently, but a lot of it comes from security checklists from people saying did you add this check? Sure adding a device integrity check may stop at least one malicious actor, but is it worth the cost? To most companies, they’re going to say they don’t understand or care about the impact.

    They could just go back to key fobs since those can’t run arbitrary code.





  • Surveillance pricing usually makes people think per-person pricing, but the law goes further than just that.

    I worked on an electronic shelf label project at a (now defunct) retail project. I’m less worried about them trying to target prices per user while in a store because there are some difficult hardware and software challenges trying to show a price to one person (like what if two people are looking at it.) Showing a per-user price per app is trivial. There’s also laws in most states that require you to pay the price shown on the price tag and trying to target per person risks failing that, though that depends on state enforcement. The system I worked at linked the prices to the point of sale system to ensure you paid the lowest price shown on any price tag in the last few hours (though that was company policy to make complying with the law easier.)

    What I am worried about is prices dynamically changing based micro trends like water getting more expensive on warm days. Some people might say that increase prices means increased supply to meet that demand, the real risk is retailers being able to micro optimize prices to better capture consumer surplus as profits. A consumer is un-prepared for that and the consumer will not benefit.


  • 15.0 adds support for OIDC tokens being handed to Actions workflows compatible with GitHub Actions. I was excited to upgrade because I wanted to continue doing cosign Docker image signing, but then I found out that the Cosign transparency log doesn’t support Forgejo. Looks like I need an alternative.

    My next biggest problem is the Actions workflow itself. I setup Docker in Docker, but turns out there’s a bit of work in preparing the runners to be on par with what I used on GitHub.

    Otherwise, I’ve found Forgejo to be quite good and almost all my private repos are moved over.









  • I thought this was using SDKs embedded in apps and advertising platforms. This is a different threat model. You need to block ads and prefer using websites instead of apps which have more access to device info like the advertising ID.

    If you’ve got an Android, go to Settings, search for ads, and find the advertising ID and delete the ID. It’s a stable identifier that can be used to identify your phone.

    Switch to more private browsers like Firefox for Mobile and install uBlock Origin.

    EDIT: I’m not saying this will protect you against IMSI catchers or tower based drag nets. In addition to not bringing your phone, when you do go home you need an entirely different set of tools to protect yourself.