This commit is contained in:
@ -3,7 +3,7 @@ title: Secrets in Repos
|
|||||||
date: 2025-05-22
|
date: 2025-05-22
|
||||||
-->
|
-->
|
||||||
|
|
||||||
# # Secrets in Repos
|
# Secrets in Repos
|
||||||
|
|
||||||
Storing secrets in cleartext in a repo is forbidden, obviously.
|
Storing secrets in cleartext in a repo is forbidden, obviously.
|
||||||
|
|
||||||
@ -36,7 +36,8 @@ can be used.
|
|||||||
Make sure to store the passphrase safely and securely in a password manager or so, otherwise you can not get to your data any longer or everyone can do so.
|
Make sure to store the passphrase safely and securely in a password manager or so, otherwise you can not get to your data any longer or everyone can do so.
|
||||||
|
|
||||||
|
|
||||||
**Remark**
|
## Remark: Problems with passphrase input
|
||||||
|
|
||||||
Sometimes, gpg tries to ask for the passphrase via the configured pinentry app, which sometimes fails. In those cases add
|
Sometimes, gpg tries to ask for the passphrase via the configured pinentry app, which sometimes fails. In those cases add
|
||||||
|
|
||||||
```
|
```
|
||||||
|
Reference in New Issue
Block a user