Update documentation on keys/identities
Dependencies
- [2]
NT22VBIWAdd key and configuration info - [3]
AFXHW7MXSwapped associativity figures - [4]
VLTCDWTCMoved files (new permissions format) - [5]
SCSV2FNSReboot - [6]
GLUD3ZVFGenerating the reference - [7]
AJ32E5LBAdd custom.css to justify align content paragraphs and enable hyphenation - [8]
LYR3UWPMAdd workflows chapter with page about channels - [9]
HKJIGLCDConflict resolution
Change contents
- file move: keys.md → identities.md
- replacement in src/identities.md at line 1
# Pijul keys# Pijul identities - replacement in src/identities.md at line 3
Pijul keys are used to identify patch authors in a manner which provides greater security and control than simply mapping authors to a name and email address. The inclusion of a name and email address can be spoofed in a way that a key signature cannot. In addition, Pijul plans to take advantage of the fact that a user's name and e-mail address are no longer tied to their submitted patches, allowing users to later change the name and e-mail address that other users see when they look at previously submitted patches.Pijul identities are used to identify patch authors in a manner which provides greater security and control than simply mapping authors to a name and email address. The inclusion of a name and email address can be spoofed in a way that a key signature cannot. In addition, Pijul plans to take advantage of the fact that a user's name and e-mail address are no longer tied to their submitted patches, allowing users to later change the name and e-mail address that other users see when they look at previously submitted patches. - replacement in src/identities.md at line 7
## Generating keys## Generating identities - replacement in src/identities.md at line 9
Users can generate a new key using `pijul key generate <name>`. The name used for this key is not required to bear any relationship to a nest username or SSH identity. During key generation, users will be asked for a password; on success, the location of the generated key will be displayed to the user (it should be the same directory as your [global configuration](configuration.md)). Pijul currently allows for the generation of one key at a time.Users can generate a new identity using `pijul identity new [name]`. The name used for this identity is not required to bear any relationship to a nest username or SSH identity. During identity generation, users will be asked for a password; on success, the location of the generated key will be displayed to the user (it should be the same directory as your [global configuration](configuration.md)). Pijul currently allows for the generation of one identity at a time. - replacement in src/identities.md at line 11
## Proving keys## Proving identities - replacement in src/identities.md at line 13
`pijul key prove [options] <remote>` is used to associate a key with a remote/nest identity. Patches submitted before using `pijul prove` will show only the key as the author.`pijul identity prove [options] <remote>` is used to associate an identity with a remote/nest identity. Patches submitted before using `pijul prove` will show only the key as the author. - replacement in src/identities.md at line 15
Example (after key generation) :Example (after identity generation) : - replacement in src/identities.md at line 17
pijul key prove <your_username>@ssh.pijul.compijul identity prove <your_username>@ssh.pijul.com - replacement in src/getting_started.md at line 21
Users can read more about keys in [the manual section on keys](keys.md).Users can read more about keys in [the manual section on identities](identities.md). - replacement in src/SUMMARY.md at line 8
- [Pijul keys](./keys.md)- [Pijul identities](./identities.md)