Last updated: September 4, 2024 at 07:26 PM
Summary of Reddit Comments on "Argon2id"
Argon2id Configuration
- Defaults for Argon2id are considered sufficient and recommended by many users: "The defaults for Argon2id are completely sufficient."
- Adjusting certain parameters like iterations, memory, and parallelism can improve security while balancing login time: "Higher parallelism combined with higher memory can improve security while keeping login time constant."
- Users suggest experimenting with different settings to find the optimal balance for security and operating speed: "I would try hardening your settings to see what happens."
- Recommended minimum configuration for Argon2id includes:
- Memory: 19 MiB
- Iteration count: 2
- Parallelism: 1
- The default settings for Argon2id are more secure than PBKDF2-SHA256: "The default configuration for Argon2id is significantly better than the default configuration for PBKDF2-SHA256."
Benefits of Argon2id
- Argon2id is preferred over PBKDF2 due to its higher resistance against GPU-based attacks: "Argon2 is superior to PBKDF especially when it comes to gpu based attacks."
- Password cracking resistance is significantly increased with Argon2id compared to PBKDF2: "Stay with Argon2."
Customization and Performance
- Customizing Argon2id parameters can potentially improve security: "You can always change back."
- Balancing memory, iterations, and parallelism is crucial for maximizing security without sacrificing user experience: "It takes 6-8 seconds on default settings or higher? That definitely doesn't sound right."
- Users recommend starting with the default settings and adjusting based on performance: "Defaults are more than adequate provided your main password is sufficiently strong."
- Take caution when adjusting settings to ensure compatibility with different devices: "There's more incentive to stick with the defaults now."
User Experience and Efficiency
- Testing the impact of parameter changes on all devices is crucial for an optimal user experience: "Remember to test the login/unlock delay on all of your devices/apps after each change."
- Increasing parallelism may not always improve unlock time and can impact security: "On desktop/web it runs on only 1 thread."
Device-Specific Recommendations
- Recommendations for iOS users include adjusting memory and iterations to account for device limitations: "For iOS, if you use the Auto-fill and do not unlock using biometrics, you indeed have a memory limit."
- Considering device specifications when customizing Argon2id settings is important for performance: "Am I to assume that means 3x800K in PBKDF2 then?"
Practical Guidance
- Users are advised to log out of all devices before changing Argon2id settings to avoid potential issues: "You MUST log out EVERY single Bitwarden client BEFORE you change to Argon2."
- Consider the trade-off between security and efficiency when adjusting Argon2id parameters: "Due to iOS limitations, then there is no point in increasing parallelism."
Additional Information
- Users can refer to specific resources like the OWASP cheat sheet for Password Storage for further guidance on Argon2id settings.
- Argon2id is recommended as a default setting for memory-constrained environments following the RFC9106 recommendations.