view the rest of the comments
Software Gore
Welcome to /c/SoftwareGore!
This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!
Remember to read the rules before you make a post or comment!
Community Rules - Click to expand
These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)
- This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
- Please keep all discussions in English. This makes communication and moderation much easier.
- Only post content that's appropriate to this community. Inappropriate posts will be removed.
- NSFW content of any kind is not allowed in this community.
- Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
- Do not repost media that has already been posted in the last 30 days. Such reposts will be deleted. Non-original content and reposts from external websites are allowed.
- Absolutely no discussion regarding politics are allowed. There are plenty of other places to voice your opinions, but fights regarding your political opinion is the last thing needed in this community.
- Keep all discussions civil and lighthearted.
- Do not promote harmful activities.
- Don't be a bigot.
- Hate speech, harassment or discrimination based on one's race, ethnicity, gender, sexuality, religion, beliefs or any other identity is strictly disallowed. Everyone is welcome and encouraged to discuss in this community.
- The moderators retain the right to remove any post or comment and ban users/bots that do not necessarily violate these rules if deemed necessary.
- At last, use common sense. If you think you shouldn't say something to a person in real life, then don't say it here.
- Community specific rules:
- Posts that contain any AI-related content as the main focus (for example: AI “hallucinations”, repeated words or phrases, different than expected responses, etc.) will be removed. (polled)
You should also check out these awesome communities!
- Tech Support: For all your tech support needs! (partnered)
- Hardware Gore: Same as Software Gore, but for broken hardware.
- DiWHY - Questioning why some things exist...
- Perfect Fit: For things that perfectly and satisfyingly fit into each other!
How feasible is it to attack argon2id with that method?
argon2id is one of those newer algorithms created specifically to make cracking infeasible and protect against certain side channel attacks.
An example performance from an Nvidia 90HX for LUKS is:
So correctly implemented, basically impossible lol.
Hashcat also added recent support for argon2id standalone and keepassxc db, so I'll see if I can run my own benchmark just to see what it shows.
Thanks! I was curious because I am using keepass and I do use argon2id lol. I was a bit skeptical because the 2s benchmark parameter seems oddly small, but nice knowing that it is actually quite good.
On a GTX 1660:
For some context, my keepassxc on my PC registers about t=50 for a 1 second unlock delay, so the example benchmark t=2 is faster than an IRL example, hence why the reference argon2id is much lower with only an additional transform round (t=3).
But yeah it's definitely good, and since argon2id allows you to set the parameters (memory, transform rounds, parallell) you can go make it hilariously indestructible if you feel like waiting like 30 seconds to unlock a DB lol.