-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd-cryptenroll: add page #10731
Conversation
Hello there, I stumbled upon systemd-cryptenroll today and when trying to understand it, I found it had no TLDR yet. I tried to make it as compact as possible, but the very dynamic parameter set of this command did not allow me to compress it further without leaving out important points. Furthermore, I had to use H2-Headings to distance the different Unlocking Methods from each other. I wasn't able to find a relatable / about as complex example to base this one on, but I would be inclined to adapt this pull request if you could provide me with one. Also, the Heading/Introduction had to be larger than normal because of the important distinction from the system boot behavior defined in crypttab and to tell the User that the volume needs to be unlocked by systemd-cryptenroll via a currently present Method to make any changes.
This comment was marked as outdated.
This comment was marked as outdated.
I'd propose removing all semi-duplicate "Unlock with FIDO2-Device" and "Unlock with Key-File" examples.
|
Removing all semi-duplicate |
The examples using That would remove another 3 examples, bringing us down to 12. An now I'm not sure what to cut next. |
Remove extra H2-Headlines Shorten the Description.
This comment was marked as resolved.
This comment was marked as resolved.
Fix Errors in Heading
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a Whitespace at the end of line 29.
Make Heading more precise and add recommendation to update initramfs. Add missing parameters to command examples Correct "fido" to "fido2"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to tldr and thanks for your contribution. I have some suggestions for this page.
We generally prefer to not leave spaces between /
(slashes) across our pages.
Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
Hello there, I stumbled upon systemd-cryptenroll today and when trying to understand it, I found it had no TLDR yet.
I tried to make it as compact as possible, but the very dynamic parameter set of this command did not allow me to compress it further without leaving out important points. Furthermore, I had to use H2-Headings to distance the different Unlocking Methods from each other.I wasn't able to find a relatable / about as complex example to base this one on, but I would be inclined to adapt this pull request if you could provide me with one.Also,
the Heading/Introduction had to be larger than normalbecause of the important distinction from the system boot behavior defined in crypttab and to tell the User that the volume needs to be unlocked by systemd-cryptenroll via a currently present Method to make any changes.EDIT / TODO: I read the content guidelines a bit too late and need to slim the tldr before it can be reviewed and accepted.common
,linux
,osx
,windows
,sunos
,android
, etc.