3 ms·
I think boring-ness is the crux of it, for me. From what I've understood, 128-bits is fine-in-practice, unless you're an extremely high-value target who is als
by Retr0id 4y ago
I think boring-ness is the crux of it, for me.
From what I've understood, 128-bits is fine-in-practice, unless you're an extremely high-value target who is also feeling unlucky. Even if I was a whistleblower under an authoritarian regime, I'd feel pretty safe using Age in its current form (at the very least, I'd have bigger things to worry about).
However, it's not quite boring enough - the fact that this conversation is happening at all attests to that fact. It would cost almost nothing to increase file key size to 256 bits, and so IMHO it should be considered for an "age v2" - but at the same time, not something people should be alarmed about in the current implementation. (with the caveat that I'm not exactly qualified to make that assertion)
- loup-vaillant 4y ago> IMHO it should be considered for an "age v2" Definitely, though personally I wouldn't go as far as recommend we make a version 2 just for this. The downsides of such a change are not worth the arguably extremely slim security benefit. (And I agree with Age author it's not worth warning users about either. Not now in 2023.)
- Retr0id 4y agoRight. I don't think this is a reason alone to make breaking changes, but if a new version is coming out for whatever reason(s), it should be bundled in with the other changes.