You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,18 @@ To load the configuration file into `archinstall` run the following command
56
56
archinstall --config <path to user config file or URL> --creds <path to user credentials config file or URL>
57
57
```
58
58
59
+
### Credentials configuration file encryption
60
+
By default all user account credentials are hashed with `yescrypt` and only the hash is stored in the saved `user_credentials.json` file.
61
+
This is not possible for disk encryption password which needs to be stored in plaintext to be able to apply it.
62
+
63
+
However, when selecting to save configuration files, `archinstall` will prompt for the option to encrypt the `user_credentials.json` file content.
64
+
A prompt will require to enter a encryption password to encrypt the file. When providing an encrypted `user_configuration.json` as a argument with `--creds <user_credentials.json>`
65
+
there are multiple ways to provide the decryption key:
66
+
* Provide the decryption key via the command line argument `--creds-decryption-key <password>`
67
+
* Store the encryption key in the environment variable `ARCHINSTALL_CREDS_DECRYPTION_KEY` which will be read automatically
68
+
* If none of the above is provided a prompt will be shown to enter the decryption key manually
69
+
70
+
59
71
# Help or Issues
60
72
61
73
If you come across any issues, kindly submit your issue here on Github or post your query in the
0 commit comments