aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--issues/add-lib.md11
-rw-r--r--issues/add-log-tooling.md16
-rw-r--r--issues/add-types.md9
-rw-r--r--issues/add-verify-tooling.md14
4 files changed, 41 insertions, 9 deletions
diff --git a/issues/add-lib.md b/issues/add-lib.md
new file mode 100644
index 0000000..18efb93
--- /dev/null
+++ b/issues/add-lib.md
@@ -0,0 +1,11 @@
+**Title:** Add library </br>
+**Date:** 2021-12-09 </br>
+**Status:** ongoing in branch rgdd/pkg </br>
+
+# Summary
+Refactor pkg/types from sigsum-log-go into a stand-alone Go library.
+
+# Description
+The pkg/types part of sigsum-log-go needs refactoring after the ssh signing
+format proposal is done. We also want to make the parts that are generally
+useful into a stand-alone library without any non-standard dependencies.
diff --git a/issues/add-log-tooling.md b/issues/add-log-tooling.md
new file mode 100644
index 0000000..7e961cb
--- /dev/null
+++ b/issues/add-log-tooling.md
@@ -0,0 +1,16 @@
+**Title:** Add log tooling </br>
+**Date:** 2021-12-09 </br>
+
+# Summary
+Add a command-line utility that makes log interactions easy.
+
+# Description
+This issue require design considerations before getting started. Minimum
+functionality probably includes the ability to do relevant formatting (like
+outputting serialized blobs to be signed or ASCII key-value pairs for
+submission), as well as an "upload" command that is smart enough to wait for
+inclusion with regards to a cosigned tree head. It would also be good to think
+about how to make uploads convenient if there are multiple submissions.
+
+(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.)
diff --git a/issues/add-types.md b/issues/add-types.md
deleted file mode 100644
index 69ef854..0000000
--- a/issues/add-types.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Add types
-There is currently a types package in sigsum-log-go. It should be moved over
-here with the goal of being a small dependency for the log and future tooling.
-
-Some steps that this issue involves:
-- [ ] Determine what should (not) be in types package
-- [ ] Import and refactor
-- [ ] Increase test coverage
-- [ ] Add missing functionality like verification of proofs, etc.
diff --git a/issues/add-verify-tooling.md b/issues/add-verify-tooling.md
new file mode 100644
index 0000000..a6eb305
--- /dev/null
+++ b/issues/add-verify-tooling.md
@@ -0,0 +1,14 @@
+**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.)