aboutsummaryrefslogtreecommitdiff
path: root/issues/add-verify-tooling.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@mullvad.net>2022-03-30 20:13:59 +0200
committerRasmus Dahlberg <rasmus@mullvad.net>2022-03-30 20:13:59 +0200
commitf801aee1378f536a41f0eb5a299787a28d983137 (patch)
tree6e0aba5e699736adf4c122fd86894531d12f7fa4 /issues/add-verify-tooling.md
parent999cf63440bb08bd2588b924a8a4309c7273adff (diff)
move issues into a common pad
Diffstat (limited to 'issues/add-verify-tooling.md')
-rw-r--r--issues/add-verify-tooling.md14
1 files changed, 0 insertions, 14 deletions
diff --git a/issues/add-verify-tooling.md b/issues/add-verify-tooling.md
deleted file mode 100644
index a6eb305..0000000
--- a/issues/add-verify-tooling.md
+++ /dev/null
@@ -1,14 +0,0 @@
-**Title:** Add verify tooling </br>
-**Date:** 2021-12-09 </br>
-
-# Summary
-Add a command-line utility that makes log verification easy.
-
-# Description
-This issue requires design considerations before getting started. The goal is
-to have a verify tool that checks if some data is signed and transparency logged
-without any outbound network connections. It should be possible to configure
-which policy to use for known logs and required witnesses.
-
-(Remark: there is no strict requirement that this has to be in Go. If anyone
-wants to work on tooling in, say, rust or python, that would be welcomed too.)