summaryrefslogtreecommitdiff
path: root/comments.txt
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2019-05-05 01:32:54 +0200
committerFlorian Dold <florian.dold@gmail.com>2019-05-05 01:32:54 +0200
commit85f92f2d765c1e6d6473b7205bcf9fbffad69ae9 (patch)
tree0675757f1909be0c4e79cb94c24f88beb94c6fc7 /comments.txt
parentaf9ef9393612917fb13621af675865b0000d989d (diff)
downloaddold-thesis-phd-85f92f2d765c1e6d6473b7205bcf9fbffad69ae9.tar.gz
dold-thesis-phd-85f92f2d765c1e6d6473b7205bcf9fbffad69ae9.tar.bz2
dold-thesis-phd-85f92f2d765c1e6d6473b7205bcf9fbffad69ae9.zip
misc
Diffstat (limited to 'comments.txt')
-rw-r--r--comments.txt3
1 files changed, 1 insertions, 2 deletions
diff --git a/comments.txt b/comments.txt
index d3a3e34..eccce20 100644
--- a/comments.txt
+++ b/comments.txt
@@ -16,8 +16,8 @@ to the more abstractly described protocols of Chapter 3. It is not simply that y
instantiating earlier mechanisms with concrete primitives; much more seems to be going
on. Are there concrete claims being made as to the security of these constructions?
+
- Fix overfull hboxes
-- Fix uses of "for example", e.g. and i.e.
- Check notation for numbers
- consistency of list capitalization
- include auditor tables in 4.3 (Space usage by database table)
@@ -25,7 +25,6 @@ on. Are there concrete claims being made as to the security of these constructio
- Proof-read references (capitalization in titles)
- transition to chapter 5?
- connection of BSC to Taler (at end of Chapter?)
-- update payto draft and point to URL
Table 4.4: