• 1 Post
  • 101 Comments
Joined 8 months ago
cake
Cake day: March 9th, 2024

help-circle
  • Sucks that I have to preface but people can be jumpy here. This is genuine curiosity, I’m actually asking, because it’s really probably something I should already know. Can you explain the nuance to me please?


    My understanding, speaking mostly of apps/websites, I know jobs can be much different:

    Most places have the first factor as a password.

    First factor (or “login”) = username+password pair.

    For the longest time that was all there was, “your login” was just a login, which meant a username and password combination. Then 2FA/MFA (“2 factor authentication / multi-factor authentication”) came along in the form of username+password combo plus SMS/email/Google Authenticator/Yubikey/etc to verify as the 2nd form of authentication. You can have 3FA 4FA 5FA whatever if you want and if it’s supported by the app/website. So 2FA is MFA, but MFA is not necessarily 2FA.

    I know jobs can be set up a lot differently.





  • For me it’s the high-horse holier than thou attitude most of them seem to carry in online conversations. I know a fee vegans and they are mostly fine in person after the first few months of radicalization, but I imagine they just suppress it in person to maintain the acquaintanceship and then bitch in their vegan echo chambers about how “my co-worker who knows I’m vegan had the audacity to order a hamburger and eat it in front of me knowing I’m vegan, does he know he’s destroying the world with that Burger… AITA?”

    If you’re looking for scientific answers, good luck they, Inrhjnjbmost people stop worrying about micromanaging people after a few years of academia.






  • I believe that is the case, if you inspected the HTTP headers and found if to show Linux instead of Windows. my last experience with that would have been years ago. Arch does like to compile things from source instead of using binary blobs, and compilers and configs can undo a lot of the work the torproject has done to combat fingerprinting, which is why it’s recommended to run the pre-built binary and install no plugins. However it’s important to note that it ALSO gives you a unique JavaScript fingerprint every time, when tools use as much information as possible to generate a fingerprint, because it generates new information on every reload. That’s why OPSEC is important and for can’t help you if you use it wrong. If you login to 2 different unlinked sites in the same session, and you don’t want them to be linked, too bad now they’re linked via JS fingerprinting. JavaScript is more or less a programming language within the browser, and you’ll never escape JavaScript fingerprinting. Which is why it’s important to learn how to use tor properly, and leave JS disabled as much as you can.

    One thing you can do with your arch build is use the fingerprinting tool to see how unique you are, then get a new identity, then go back and do it again. Does it now say you’re one of 2 people who have used the tool, or does it show you’re (again) unique? If the latter, then it’s working (at least enough) properly.