| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is tested as far as possible. However, the actual extend
case can only be tested in about three weeks from now when the
next publication is out. I have done module-testing with a
mockup extend call, so chances are great the final test will
be passed.
|
|
|
|
|
|
|
| |
... done up until the point where I need to wait for the
timestamps to become extendible. So doing a milestone commit
to make sure the work is inside the archive. Actual writing of the
extended timestamp is missing.
|
|
|
|
| |
does not contain actual implementation
|
| |
|
|
|
|
|
| |
The way tlvrecords are processed is changed in order to
provide better extensibility for further work.
|
| |
|
| |
|
|
|
|
|
| |
We now use a higher-level verification function as suggested
by GuardTime.
|
|
|
|
|
|
|
|
| |
unfortunately, there seems to be a problem with the GuardTime API, so
that I need their support before being able to carry on. Once I
receive it, it should be fairly quick to complete the function. I am
commiting this work as I do not know how long it will take to receive
an answer.
|
|
|
|
| |
bugfix: the initial vector was used incorrectly during hash computation.
|
| |
|
| |
|
|
It will support various maintenaince operations, including
verification of signatures in the future. To match its new
scope, it also has been renamed.
|