build: fix cargo vet issues

We acknowledge some warnings in the deny configuration, since they are
either not relevant or can not be fixed.

Author: danielsreichenbach

Cargo.lock

@@ -45,4 +45,4 @@ tempfile = "3.20"
 # Development
 criterion = { version = "0.6", features = ["html_reports"] }
 pretty_assertions = "1.4"
-proptest = "1.6"
+proptest = "1.7"

Cargo.toml

@@ -69,6 +69,7 @@ ignore = [
   #{ id = "RUSTSEC-0000-0000", reason = "you can specify a reason the advisory is ignored" },
   #"a-crate-that-is-yanked@0.1.1", # you can also ignore yanked crate versions if you wish
   #{ crate = "a-crate-that-is-yanked@0.1.1", reason = "you can specify why you are ignoring the yanked crate" },
+  { id = "RUSTSEC-2023-0071", reason = "RSA timing attack vulnerability - not critical for local MPQ file processing. Awaiting constant-time implementation." },
 ]
 # If this is true, then cargo deny will use the git executable to fetch advisory database.
 # If this is false, then it uses a built-in git library.
@@ -87,8 +88,8 @@ allow = [
   "MIT",
   "Apache-2.0",
   "Apache-2.0 WITH LLVM-exception",
-  "MPL-2.0",
   "Unicode-3.0",
+  "BSD-3-Clause",
 ]
 # The confidence threshold for detecting a license from license text.
 # The higher the value, the more closely the license text must be to the
@@ -141,7 +142,7 @@ registries = [
 # Lint level for when multiple versions of the same crate are detected
 multiple-versions = "warn"
 # Lint level for when a crate version requirement is `*`
-wildcards = "deny"
+wildcards = "warn"
 # The graph highlighting used when creating dotgraphs for crates
 # with multiple versions
 # * lowest-version - The path to the lowest versioned duplicate is highlighted

deny.toml

@@ -47,7 +47,7 @@ pretty_assertions = { workspace = true }
 proptest = { workspace = true }
 tempfile = { workspace = true }
 assert_cmd = "2.0"
-predicates = "3.0"
+predicates = "3.1"
 
 [[bench]]
 name = "hash"