45 |
Past: |
Past: |
46 |
----- |
----- |
47 |
|
|
48 |
2003-05-16 [5.5h, 13.00-18.30]: |
2003-05-16 [14.5h, 13.00-20.30; 22.00-05.00]: |
49 |
|
|
50 |
- work towards making libvob and fenfire work on Kaffe |
- work towards making libvob and fenfire work on Kaffe |
51 |
- submit patches to Kaffe |
- submit patches to Kaffe |
52 |
|
- more thinking about vobs, trying to come up with |
53 |
|
way to get started on structured graphics vobs |
54 |
|
- learn about XML signature: can we come up with a way |
55 |
|
to use one-time signatures with XML sig? (register |
56 |
|
our own algorithm) -- actually doesn't require |
57 |
|
registering: XML sig uses URIs! There are free |
58 |
|
implementations of XML sig; however, we may consider |
59 |
|
XML sig as too heavyweight (need to think). |
60 |
|
We could also say: only RDF blocks are signed |
61 |
|
(for RDF, meaning is more or less well-defined); |
62 |
|
so the sig block simply gives the hash of the RDF block. |
63 |
|
-- It's interesting that there is no standard |
64 |
|
one-time signature algorithm-- I mean there are algorithms, |
65 |
|
but abstract descriptions, not on the level that specifies |
66 |
|
which exact bytes the output is for a given input. |
67 |
|
- Think about timestamping; to provide non-repudability |
68 |
|
(one can't say one signed a given block) one would need |
69 |
|
to be able to prove that a block was signed before |
70 |
|
the key was revoked? Otherwise to say you didn't sign |
71 |
|
a given block, you'd just need to revoke the key that |
72 |
|
signed it... and claim that the signature was created |
73 |
|
after you've revoked the key. However, non-repudability |
74 |
|
is not a central goal of Storm; it may be ok if it is |
75 |
|
only archievable if a trusted third party timestamping |
76 |
|
service is available. |
77 |
|
- Figure out how at the expense of some more space & time, |
78 |
|
one-time signatures can be made any-time; need to think |
79 |
|
about whether that is useful... :-) [may not be new, |
80 |
|
but if it is, may be publishable] |
81 |
|
- Note that there are *many* introductions explaining that |
82 |
|
one-time signatures can only be used one or a limited |
83 |
|
number of times. Therefore, it seems this is new. |
84 |
|
- Start writing this up. Notice that ACM CCS deadline |
85 |
|
is tonight and make brave-hearted but folly-ish attempt |
86 |
|
to write an article. ;-) Give up. |
87 |
|
|
88 |
2003-05-15 [8h, 14.00-24.00 with breaks]: |
2003-05-15 [8h, 14.00-24.00 with breaks]: |
89 |
|
|