Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
tahoe-ssk
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
PrivateStorage
tahoe-ssk
Commits
f174e291
Commit
f174e291
authored
1 year ago
by
Jean-Paul Calderone
Browse files
Options
Downloads
Patches
Plain Diff
note we don't do some things
parent
96941786
No related branches found
No related tags found
1 merge request
!17
Point out some security-related features are missing
Pipeline
#5398
passed
1 year ago
Stage: test
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+6
-1
6 additions, 1 deletion
README.md
with
6 additions
and
1 deletion
README.md
+
6
−
1
View file @
f174e291
...
@@ -13,7 +13,12 @@ However, its APIs are intended to be easy to integrate with such an implementati
...
@@ -13,7 +13,12 @@ However, its APIs are intended to be easy to integrate with such an implementati
*
SDMF write, read, and verify capabilities can be parsed and serialized.
*
SDMF write, read, and verify capabilities can be parsed and serialized.
*
SDMF shares can be deserialized, decoded, and decrypted.
*
SDMF shares can be deserialized, decoded, and decrypted.
*
The cryptographic integrity and authenticity is not verified.
*
The cryptographic integrity is not verified:
*
a share's block hashes are not checked against the share's block hash tree
*
the root of the computed share hash tree is not checked against share's pre-computed share hash tree root
*
The cryptographic authenticity is not verified:
*
signatures on the data are not checked
*
Plaintext can be encrypted, encoded into shares, and the shares serialized to bytes.
*
Plaintext can be encrypted, encoded into shares, and the shares serialized to bytes.
*
Not all fields of the shares contain correctly initialized values.
*
Not all fields of the shares contain correctly initialized values.
*
Enough fields are correctly populated to recover the original plaintext.
*
Enough fields are correctly populated to recover the original plaintext.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment