[Webfunds-commits] java/webfunds TODO_SCW
Edwin Woudt
edwin@cypherpunks.ai
Mon, 28 Aug 2000 13:38:24 -0400 (AST)
edwin 00/08/28 13:38:24
Modified: webfunds TODO_SCW
Log:
- Removed fixed secret key matches public key check.
- Removed some irrelevant comments.
- Fixed numbering of feature requests. ;-)
Revision Changes Path
1.12 +4 -18 java/webfunds/TODO_SCW
Index: TODO_SCW
===================================================================
RCS file: /home/webfunds/cvsroot/java/webfunds/TODO_SCW,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- TODO_SCW 2000/08/28 16:31:12 1.11
+++ TODO_SCW 2000/08/28 17:38:23 1.12
@@ -2,13 +2,6 @@
I. Sanity checking that is needed:
- I.c) Secret Key
-
- + secret key matches contract public key - would be nice to have a
- check as it is being entered, currently it is checked only during
- the signing process.
-
-
II. Presentation.
III. Coding comments (minor).
@@ -18,13 +11,6 @@
is fixed for cleartext sigs (OpenPGP) and hashes (Ricardian
contracts)?
- Note: see System.getProperty("line.separator");
-
- (This is the local property, whereas the "\r\n" is special
- OpenPGP standard (99%) newline for cleartext sigs, also used
- (100%) by Ricardo for hashes.)
-
-
IV. Feature Requests!
i) Different methods for accessing keys.
@@ -55,10 +41,10 @@
then the decrypted version is disposed of quickly... may not be the
case.)
- iv) additional potential sanity check: that the signed contract can
- be un-signed and contents compared with original proto-contract to
- ensure that no additional chars were introduced during the signing
- process. (defer... might think about that...)
+ iii) additional potential sanity check: that the signed contract can
+ be un-signed and contents compared with original proto-contract to
+ ensure that no additional chars were introduced during the signing
+ process. (defer... might think about that...)
V. For WebFunds.Ricardian