Today's tip: Don't partition already partitioned data using the same hash function that it has already been partitioned with.

Or: Application specific keys for hash functions are there for a reason, don't use the same for different applications.

@alva that might actually be a really bad idea since shuffle most likely doesn't use cryptographically secure random numbers.
They are most likely time based which significantly decreases the ranges of numbers to brute force.

@alva Oh ok, haven't thought ablut that so far. But should be doable by combinig the wordlists together.

@alva it allows editing the staging area directly

FSMaxB boosted

Remember: You are not responsible for dealing with someone who is "good hearted and means well, just a freak", but tires your Emotional mental capacities. Especially if the person keeps overstepping boundaries and tries to negotiate what your boundaries are.

Key takeaway: Consider your /etc/shadow to be containing essentially plain text passwords.

-> Don't reuse Linux login passwords for anything else
-> Encrypt your system partition (and be sure to configure a sensible key derivation function when setting it up using cryptsetup, I don't think they use sensible defaults yet. In other words: Tell cryptsetup to use Argon2id and optimise --iter-time and --pbkdf-* to be as slow and memory consuming as acceptable)

OMG, why can't we have nice things. Just found out that passwords in /etc/shadow are hashed using SHA-512 by default (which is the least bad option ...) but only 5000 rounds by default (not that more rounds would make it significantly more resistant against brute force in any case).

Today: Have you ever looked at the semantics of "round" in your programming language. Look at JavaScript and Python for example.

The biggest unsolved problems of applied computer science:
* floating point numbers
* date/time
* text

@alva I'm not in a union either but we're such a small startup that I only have a few programmer colleagues, if just two of us started protesting there would be a problem for the company ...

Food, environment, snark 

Food, environment, snark 

Food, environment, snark 

Food, environment, snark 

Food, environment, snark 

Just found some interesting code in jemalloc's implementation of a mutex:

if (ncpus == 1) {
goto label_spin_done;
}

github.com/jemalloc/jemalloc/b

Show more
mastodon.cloud

Generalistic and moderated instance.