Update documentation

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "search-edeks"
-version = "1.0.0"
+version = "1.1.0"
 authors = ["IronCore Labs <[email protected]>"]
 categories = ["utilities"]
 description = "Tool to search EDEK's protobuf. Can be used to find EDEKs that need to be rekeyed from an old KMS config ID."

README.md

@@ -16,7 +16,7 @@ Check out this repo and run `cargo b --release`. The binary will be at `target/r
 
 ```console
 search-edeks --help
-search-edeks 1.0.0
+search-edeks 1.1.0
 IronCore Labs <[email protected]>
 Tool to search EDEK's protobuf. Can be used to find EDEKs that need to be rekeyed from an old KMS
 config ID.
@@ -31,10 +31,12 @@ OPTIONS:
     -h, --hex            Consume and output hex formatted EDEKs
         --help           Print help information
     -i, --id <VALUE>     Sets the KMS config ID we're searching for
+    -v, --verbose        Output identifier and original EDEK (and error message if applicable). If
+                         not enabled, only identifiers will be output
     -V, --version        Print version information
 ```
 
-For example `search-edeks -f edeks.txt -i 1201 -h` would search `edeks.txt` for any EDEKs that were created using KMS config ID `1201`.
+For example `search-edeks --file edeks.txt --id 1201 --hex` would search `edeks.txt` for any EDEKs that were created using KMS config ID `1201`. It would output `matching-edeks.txt` with the one identifier per line for each EDEK that matched. It would output `broken-edeks.txt` with one identifier per line for each EDEK that wasn't parsable as an EDEK. If `--verbose` was enabled, the output would be tuples of the required input form (with the broken EDEKs additonally containing an error message).
 
 ## Releasing