@@ -1094,6 +1094,7 @@ executed within the Cargo process. They are identified with the `cargo:` prefix.
1094
1094
* ` cargo:token ` - Uses Cargo's config and ` credentials.toml ` to store the token (default).
1095
1095
* ` cargo:wincred ` - Uses the Windows Credential Manager to store the token.
1096
1096
* ` cargo:macos-keychain ` - Uses the macOS Keychain to store the token.
1097
+ * ` cargo:libsecret ` - Uses [ libsecret] ( https://wiki.gnome.org/Projects/Libsecret ) to store tokens on Linux systems.
1097
1098
* ` cargo:token-from-stdout <command> ` - Launch a subprocess that returns a token
1098
1099
on stdout. Newlines will be trimmed. The process inherits the user's stdin and stderr.
1099
1100
It should exit 0 on success, and nonzero on error.
@@ -1130,20 +1131,6 @@ In the config, add it to `global-credential-providers`:
1130
1131
global-credential-providers = [" cargo-credential-1password" ]
1131
1132
```
1132
1133
1133
- A wrapper is available for GNOME
1134
- [ libsecret] ( https://wiki.gnome.org/Projects/Libsecret ) to store tokens on
1135
- Linux systems. Due to build limitations, this wrapper is not available as a
1136
- pre-compiled binary. This can be built and installed manually. First, install
1137
- libsecret using your system package manager (for example, `sudo apt install
1138
- libsecret-1-dev` ). Then build and install the wrapper with ` cargo install
1139
- cargo-credential-gnome-secret`.
1140
- In the config, use a path to the binary like this:
1141
-
1142
- ``` toml
1143
- [registry ]
1144
- global-credential-providers = [" cargo-credential-gnome-secret" ]
1145
- ```
1146
-
1147
1134
#### JSON Interface
1148
1135
When using an external credential provider, Cargo communicates with the credential
1149
1136
provider using stdin/stdout messages passed as a single line of JSON.
0 commit comments