• 0 Posts
  • 109 Comments
Joined 1 year ago
cake
Cake day: August 25th, 2023

help-circle




  • You are missing the point, it’s not “4.5 hours a week of work” vs “absolutely nothing”, it’s 4.5 hours of work vs however long to have to work to pay for the ingredients, plus the time to make the food. If I spend an hour meal prepping and it takes me an hour and a half to pay for the ingredients, eating out at lunch only costs me 2 additional hours of my time, not 4.5

    I also don’t know what meal you are preparing where chopping veggies, searing meat, packaging and cleaning up afterwards only takes 20 minutes. Even making chili, which is the prototypical “throw everything in a pot” recipe takes me north of an hour when all is said and done









  • The add function in the example above probably traverses the call stack to see what line of the script is currently being executed by the interpreter, then reads in that line in the original script, parses the comment, and subs in the values in the function call.

    This functionality exists so when you get a traceback you can see what line of code triggered it in the error message



  • That assumes that an adversary has control of the browser

    No it doesn’t, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account

    The big reason you don’t want to send passwords over https is that some organizations have custom certs setup

    What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways

    It is better to just not send the password at all.

    How would you verify it then?

    If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in



  • The word ‘decipher’ is doing a lot of heavy lifting. I’m wondering if they socially engineered or just found it written somewhere in the house?

    You can plausibly brute force up to 4, maybe 5 words of a seed phrase. It takes longer than a normal password because every seed phrase is technically valid, so the only way to know if your brute force is successful is to generate thousands of addresses at each of the different derivation paths you may expect funds to exist at.

    The same seed phrase is used for Bitcoin, Ethereum, Monero, etc, but each currency uses the seed phrase to generate addresses in a slightly different standard. Additionally, each wallet uses a slightly different variation of that. Within each wallet is a notion of accounts, and within each account you could have dozens of addresses. You need to generate each of those addresses, and scan each cryptocurrencies blockchain to see if those addresses have ever been used.

    Realistically one of three things happened: his seed phrase was written down and they found it, it was password protected or on a drive with weak AES encryption and they cracked THAT instead, or finally, he used a hardware wallet and they exploited a firmware vulnerability to lift the PIN and transfer out funds and/or read the seed from the device