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
prepare for v4.1 release
- expose dbus::Path fields on Items and Collections
- allow creation of Items and Collections from a remembered path
- update the MSRV to 1.78 (minimum for `Cargo.lock` version 4)
- make lifetimes explicit to avoid Clippy complaints
This crate is a knock-off of the [hwchen/secret-service](https://crates.io/crates/secret-service) crate, which is
9
-
currently at version 4 and uses [zbus](https://crates.io/crates/zbus) to access the secret service. The basic
10
-
collection, item and search APIs in this crate are meant to work the same as the blocking APIs in the zbus-based crate.
11
-
If they don't, please file a bug.
8
+
This crate started as a knock-off of the [secret-service](https://crates.io/crates/secret-service) crate, which uses [zbus](https://crates.io/crates/zbus) to access the secret service. The basic collection, item and search APIs in this crate are meant to work the same as the blocking APIs in the zbus-based crate. If they don't, please file a bug.
12
9
13
-
Why do a knock-off? So that folks who write synchronous Rust apps that access the secret service (typically through
14
-
the [hwchen/keyring](https://crates.io/crates/keyring) crate) are not required to add an async runtime. Because this
15
-
knock-off uses lib-dbus, it doesn't require an async runtime.
16
-
17
-
Why is this crate starting at version 4? Since its API matches a particular version of the dbus-based crate, I figured
18
-
it would be clearest if its version number matched that version as well.
10
+
Why do a knock-off? So that folks who write synchronous Rust apps that access the secret service (for example, [Keyring](https://open-source-cooperative/keyring-rs/wiki/Keyring) clients) are not required to add an async runtime. Because this knock-off uses lib-dbus, it doesn't require an async runtime.
19
11
20
12
## Usage
21
13
22
-
For code usage examples, see the [documentation](https://docs.rs/dbus-secret-service).
14
+
For code usage examples, see the [documentation](https://docs.rs/dbus-secret-service) and the [example program](https://github.com/open-source-cooperative/dbus-secret-service/blob/main/examples/example.rs).
23
15
24
-
This crate has no default features, and requires no features to run. If you need your secrets to be encrypted on their
25
-
way to and from the secret service, then add one of the crypto features:
16
+
This crate has no default features, and requires no features to run. If you want your secrets to be encrypted on their
17
+
way to and from the secret service (highly recommended), then add one of the crypto features:
26
18
27
19
*`crypto-rust` uses pure Rust crates for encryption.
28
20
*`crypto-openssl` uses the openssl libraries for encryption (which must be installed).
29
21
30
-
See the [documentation](https://docs.rs/dbus-secret-service) for details on how to specify use of an encrypted session.
22
+
See the [documentation](https://docs.rs/dbus-secret-service) for details on how to connect to the Secret Service with an encrypted session.
31
23
32
-
To _build_ a project that uses this crate, your development machine will need
33
-
to have the dbus development headers installed,
34
-
and the openssl development headers for the `crypto-openssl` feature.
35
-
To _run_ an application that uses this crate,
36
-
your machine will need to have `libdbus` installed
37
-
(almost all do),
38
-
and the openssl libraries for the `crypto-openssl` feature.
39
-
If you want to avoid this runtime requirement,
40
-
you can specify the `vendored` feature at build time:
41
-
this will statically link the needed libraries with your executable.
24
+
To _build_ a project that uses this crate, your development machine will need to have the dbus development headers installed, and the openssl development headers for the `crypto-openssl` feature. To _run_ an application that uses this crate, your machine will need to have `libdbus` installed (almost all do), and the openssl libraries for the `crypto-openssl` feature. If you want to avoid this runtime requirement on clients, you can specify the `vendored` feature at build time: this will build and statically link the needed libraries with your executable.
* SecretService: initialize dbus, create plain or encrypted session connection.
29
+
* Collections: create, delete, search.
30
+
* Items: create, delete, search, get/set secret.
48
31
49
-
## Changelog
32
+
## Change History
50
33
51
-
v4.0.0: first release, same API as secret-service v4.0.
34
+
See [CHANGELOG.md](CHANGELOG.md).
52
35
53
36
## License
54
37
55
-
The copyright to all material in this repository belongs to the collective
56
-
of contributors who have checked material into this repository.
38
+
The copyright to all material in this repository belongs to the collective of contributors who have checked material into this repository.
57
39
58
40
All material is this repository is licensed under either of
59
41
@@ -64,8 +46,4 @@ at your option.
64
46
65
47
## Contribution
66
48
67
-
Unless you explicitly state otherwise,
68
-
any contribution intentionally submitted for inclusion in the work by you,
69
-
as defined in the Apache-2.0 license,
70
-
shall be dual licensed as above,
71
-
without any additional terms or conditions.
49
+
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
0 commit comments