#468 [Docs] Seemingly contradicting statement in encrypted_parabola.html docs

Closed
opened 2 years ago by necklace · 2 comments

In docs/gnulinux/encrypted.parabola.html it says:

NOTE: the default iteration time is 2000ms (2 seconds), if not specified when running the cryptsetup command. You should set a lower time than this; otherwise, there will be an approximately 20-second delay when booting your system. We recommend 500ms (0.5 seconds), and this is included in the prepared cryptsetup command above. Keep in mind that the iteration time is for security purposes (it mitigates brute force attacks), so anything lower than 5 seconds is probably not very secure.

How can you recommend 500ms (0.5 seconds) while also saying "anything lower than 5 seconds is probably not very secure"?

I'm guessing that last sentence was supposed to say:

anything lower than 0.5 seconds is probably not very secure

Is this right?

In `docs/gnulinux/encrypted.parabola.html` it says: > NOTE: the default iteration time is 2000ms (2 seconds), if not specified when running the cryptsetup command. You should set a lower time than this; otherwise, there will be an approximately 20-second delay when booting your system. We recommend 500ms (0.5 seconds), and this is included in the prepared cryptsetup command above. Keep in mind that the iteration time is for security purposes (it mitigates brute force attacks), so anything lower than 5 seconds is probably not very secure. How can you recommend 500ms (0.5 seconds) while also saying "anything lower than 5 seconds is probably not very secure"? I'm guessing that last sentence was supposed to say: > anything lower than **0.5** seconds is probably not very secure Is this right?
Andrew Robbins commented 2 years ago
Collaborator

Yes, you are correct. That line should instead read

anything lower than 0.5 seconds is probably not very secure

Could you submit a pull request fixing this?

Yes, you are correct. That line should instead read > anything lower than 0.5 seconds is probably not very secure Could you submit a pull request fixing this?
Andrew Robbins commented 2 years ago
Collaborator

Closed as pull #501 has been merged, fixing this issue. Thanks!

Closed as pull #501 has been merged, fixing this issue. Thanks!
Sign in to join this conversation.
Loading...
Cancel
Save
There is no content yet.