summaryrefslogtreecommitdiff
path: root/Cargo.toml
diff options
context:
space:
mode:
authorpennae <github@quasiparticle.net>2022-07-17 09:47:33 +0200
committerpennae <github@quasiparticle.net>2022-07-17 17:23:52 +0200
commitd4ed52e48eb52566dab91080eb25d8979fbb7d3e (patch)
tree5380dbf07454fa28f78ece9d1c262cc8bab00316 /Cargo.toml
parentaa3bc5459b58d6e3897d3cef8ae07d3c35d9e2a9 (diff)
downloadminor-skulk-d4ed52e48eb52566dab91080eb25d8979fbb7d3e.tar.gz
minor-skulk-d4ed52e48eb52566dab91080eb25d8979fbb7d3e.tar.xz
minor-skulk-d4ed52e48eb52566dab91080eb25d8979fbb7d3e.zip
remove zeroize dependency
this is not so much a problem as a possible source of false security for the readers. all secret keys we handle are serialized in some form, and those serialization buffers are *not* zeroed out after use. zeroing our raw buffers doesn't help much in that case, using a zero-on-free allocator would be much more helpful.
Diffstat (limited to 'Cargo.toml')
-rw-r--r--Cargo.toml1
1 files changed, 0 insertions, 1 deletions
diff --git a/Cargo.toml b/Cargo.toml
index da84734..4025383 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -31,7 +31,6 @@ subtle = "2.4.1"
url = "2.2.2"
validator = { version = "0.15", features = [ "derive" ] }
web-push = "0.9.2"
-zeroize = { version = "1.4.3", features = [ "zeroize_derive" ] }
[dev-dependencies]
hex-literal = "0.3.4"