• 0 Posts
  • 666 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2024

help-circle
  • ??? that’s not what passkeys are at all. This is just bullshit security theater.

    Passkeys are actually fairly neat, they are mostly just about forcing the user to do the thing they should be doing with passwords anyway, but standardized-ish so that the browser extension doesn’t need to figure out which form field is the username and which is the password.







  • Operator overloading is awesome in a functional language. Haskell allows for a lot of creative stuff with operators, but since they can’t have side effects, must conform to predictable types, and have specific requirements they are somewhat understandable. Idris is also very ergonomic when it comes to operators.

    C++ allowing a library to override the + operator with system("rm -rf /") is a lot less awesome.





  • all i can say is that i need to log into outlook to log into teams, because logging into teams directly is broken, but the cross site cookie work…

    Thankfully I don’t even have an MS account, but I do implore you to check out the cookies and see for yourself that they will have a specific list of domains they are valid for.

    Open the browser developer menu on an Outlook tab (F12), navigate to “Storage” → “Cookies” (may be named slightly differently in different browsers), and look at the “Domain” column in the table.

    and reading stuff like adFection really doesn’t instill confidence in opening random websites.

    The problem there is website operators selling their adspace to a literal israeli spyware company, which meant injecting adversarial javascript into their own pages. It was not a case of “user opening a random link”, rather it was the website operator themselves forwarding the user malicious JS from the “ad company”. As a user there’s generally nothing you can do to prevent this kind of attack where the website itself was compromised; besides, without another vulnerability/attack vector the impact will be limited to the website in question.


  • No, you generally should not be worried about that.

    Generally the worst thing that a website can get from you just opening a URL is (1) whether or not you’re logged in to google/facebook/etc, (2) your advertisement profile/who you are, (3) roughly where you are. All those are privacy issues, not a security issue, hence not very related to the “cybersecurity course”, and only the first one is tangentially related to being logged in.

    You should of course use various anti-tracking measures, e.g. an adblocker, “resist fingerprinting” in Librewolf, user agent faker, a good VPN, etc. That will reduce the exposure to all 3 issues above, but once again those are not security problems.

    You should also never download random bullshit to your computer. Having an actual file on disk outside the browser sandbox could indeed be an issue. You could simply forget where it came from and decide to execute it one day, or there could be some bug in some app on your OS which could trigger a code execution exploit.

    However, if your browser shares authentication details with random websites like what you are describing, you should stop using it immediately.


  • Cookies are specifically separated out per-domain. Your browser will not give a random website access to your auth cookies/localstorage for other websites. There are some awful companies which do set cross-website cookies (e.g. facebook, google, and other adware), but (1) those cookies are not auth credentials and are used mostly for fingerprinting and ad targeting, (2) should be filtered out by your browser’s tracking protection (hence “if your browser is set up correctly”).

    Realistically there is still be a way for the website to fingerprint you enough to know who you are even without cookies, so the most adversarial outcome from clicking a link is that the attacker can know that you clicked that link, along with your general location (from geoIP) and some device info.

    iirc that’s how the linux tech tips channel got into trouble.

    Nah, that was pretty much an .exe sent out by a fake sponsor, which was downloaded and executed. It then stole all browser data (including google auth cookies). Opening a link ≠ running an unsandboxed exe.


  • I have never bought and will never buy an apple thing (because it’s a super-enshittified walled garden), but honestly I’m just fine with 60Hz. My phone supports 120Hz and I have switched it back to 60Hz because it gives me a couple extra hours of battery. I can tell the difference but it doesn’t bother me one bit. I’d even be OK with 30Hz if it was an option and had a significant battery life advantage.

    Maybe having all the animations in the OS and apps turned off helps keep it not noticeable.

    Whatever is the standard going forward, I hope that there’s always an option to cut back the refresh rate in exchange for battery life, either at the time of purchase or in the settings.



  • We actually have a big shortage of talent

    That review may lead to changes in roles, responsibilities, and continued employment. Individual outcomes will be communicated directly once decisions are finalized.

    Knowing how the hiring/onboarding process works in IT — i.e. how fucking hard it is to find, hire, onboard, train and build up a working relationship with an adequate employee — I strongly doubt they have a “shortage of talent” if they’re willing to fire (or even just threaten to fire) people over what amounts to tooling use.

    Oh, also, if I got an email threatening my “continued employment” over shit like this I’d be looking for a new job ASAP. And I have been using LLMs for my work for a couple of years now.




  • I agree that in general some margin on labor can be expected to recoup capex. But ~70% is just too much, especially for the original example of a “cleaning fee” on top of the “everything else” charge that you already have to pay.

    There is no “this goes to keep the lights on” surcharge

    Actually when I still had a car and took it to my favourite shop, the itemized bill included parts, labor, and a “workshop charge” to pay their rent and stuff. Speaking to the mechanics they did actually get all the money in the “labor” item (minus payroll taxes). I liked that approach.