Cybersecurity

6893 readers

156 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 2 years ago

MODERATORS

[email protected]

Questions about Argon2id and authentication handling overall (lemmy.ca)

submitted 2 weeks ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Is it a good idea to crank up the settings in Argon2id to max (20 iterations, 100 length, salted) for applications? I'm new to the cybersecurity subject, but I assume keeping the hashing as slow as possible (and a longer hash length = fewer chances of collusion) helps fight against brute-forcing. Is that correct?

Also, what is the security of having a password logging in system that: 1: Uses the max Argon2id settings, to make the authentication slow 2: Makes it take 1–2 seconds (in a circle loading style) for it to either fail, or succeed 3: Adds a 1-second cooldown, increasing by 0.5s by every failed attempt (any successful attempt in that cooldown is ignored, it just says that it's on cooldown nevertheless)

I'm open to suggestions! (I'm not implementing everything, but thought experiments are a good place to start, IMO)

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 2 weeks ago (1 children)

It makes way more sense to implement an auth cooldown over increasing the server load for a single action. I can't speak on the ideal settings for Argon2id, but I like to think the defaults are fine in most cases.

[–] [email protected] 1 points 2 weeks ago

And increasing the hash size, to mitigate collusions? I would assume that it takes much longer to find collusions that result in a specific password's hash, if there are more digit amounts, correct?

[–] [email protected] 2 points 2 weeks ago

Use the recommemded parameters: https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-argon2-04#page-11

Also consider WebauthN/Passkeys. They are much less ressource intensive on the server but useless to an attacker when the database is leaked and as such don't rely on slowing down the crypto operations.