• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: May 31st, 2023

help-circle







  • reserves the right to sell you out

    Is Canonical actually doing that, though? Collecting data for product improvement purposes and collecting it to potentially sell to third parties are two wildly different things, and doing the former, even with the user’s consent, does not mean you automatically reserve the right to do the latter (or anything else, really) with the collected data, unless you explicitly already include that as an option and get consent for it as well. I haven’t looked into it myself, so I might be wrong here, but I’m guessing Canonical would be getting way more shit for this if they were actually reserving the right to outright sell the telemetry they’re collecting, rather than just use it for product planning and development.



  • Oftentimes, just a couple of pieces are responsible for the high price, because they’re rare in the specific color being used in the MOC. Sort the part list by price, and you’ll quickly be able to identify what the problem is, and see if you have similar pieces already that’ll do the job, or if you can just substitute a different color that’s cheaper to get, for example. It also helps to have your own collection logged on rebrickable, as it’ll show you how many of the required pieces you already own!











  • Those last three input boxes are all parameters to fine tune the operation of the key derivation function, they control the performance and hardware usage characteristics of how to derive the actual database encryption key from your password in order to make it harder to brute force.

    The Transform Rounds input essentially controls how much sequential processing power is needed by repeating a specific part of the KDF more or less often, and thus allows you to determine how long the key derivation will take every time. That’s why there’s a Benchmark button next to it - it will automatically test on your CPU and determine how many rounds are needed to produce a 1 second delay on your hardware. Which is an acceptable time to wait for your database to unlock, but bad news for someone trying to brute force your password, as it limits how many attempts different passwords they can test in a given time.

    Memory usage controls the amount of memory the KDF needs, and Parallelism controls how many parallel threads are used, both limiting how many parallel attempts at brute forcing your password a potential attacker can run on any given hardware.

    Disclaimer: I’m not a security expert, just a software developer who has come into contact with KDFs quite a bit. If I misrepresented anything above, happy for correction!