Unreleased
- Updated dependencies where reasonable
- Bumped MSRV to 1.60
- BREAKING: Updated to
zbus
3.0. This changes error types and public path fields. - BREAKING: The types exported from the crate root are now entirely async. Blocking functions have been moved into the
blocking
module. - BREAKING:
Error::Crypto
now contains a&'static str
instead of aString
. - BREAKING:
SecretService::search_items
now takes aHashMap<&str, &str>
instead ofVec<(&str, &str)>
for the attributes. - BREAKING: The
SecretService::new()
method was renamed toSecretService::connect()
to be more accurate. - BREAKING:
Error
is now marked as#[non_exhaustive]
to allow for additions to be made more easily in the future. - BREAKING: Several dead error variants were pruned.
- BREAKING:
search_items
now returns both locked and unlocked items. If an unlocked item isn't present in the list, it must be unlocked manually.
- Increased minimum
zbus
version to 1.9.2, in order to increase the minimum version of the transitive dependencynix
to at least 0.20.2, which is the firstnix
release to contain the fix for the security vulnerability described at https://rustsec.org/advisories/RUSTSEC-2021-0119 . A known issue with this version ofnix
is that it places an upper bound on the version of thebitflags
dependency; if you are depending onbitflags
, you may need to downgrade yourbitflags
version in order to upgrade to this version ofsecret-service
, which you are encouraged to do in order to ensure that you are not exposed to the aforementionednix
vulnerability. In the long term, this will be fixed by upgradingsecret-service
to use a newer version ofzbus
, which itself depends on versions ofnix
which no longer have this restriction onbitflags
.
- Updated crate's Rustdoc link
- dbus replaced by zbus, PURE RUST!
- update to 2018 edition
- BREAKING:
SsError
renamed toError
- BREAKING: variants added to
Error
- BREAKING: attributes are now
HashMap<&str, &str>
orHashMap<String, String>
instead ofVec<(&str, &str)>
. Not sure why I decided this way back when, but it could cause unexpected behavior for user: when theVec
was transformed toHashMap
internally, tuples could be lost if the keys were the same. - BREAKING:
Collection::new
andItem::new
are now private (although I don't think it was possible to use them anyways)
1.1.3
- update deps
1.1.2
- update rand
- update deps
- Fix, get_collection_* returns Error::NoResult when doesn't exist
- udpate hkdf to 0.8
- switch from rust-crypto to RustCrypto
- remove gmp dep for powm
- update rand and num
0.4.0
- gmp is now optional dependency.
- gmp upgraded to 0.3 to fix "private-in-public" warnings which will be hard errors soon.
...
0.1.0
- dependency on gmp is removed.
- rust-crypto replaced by RustCrypto.
- as a result of above, error on encrypting and decrypting blank input is fixed.