-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prototype #3
Labels
milestone
project milestone
Comments
Re: identity models Atomic Data has the same problem of how to securely manage private keys for signing (in their case, of Commits) |
gsvarovsky
added a commit
that referenced
this issue
Jan 26, 2022
Refinements to design Mindmap images
gsvarovsky
added a commit
to m-ld/m-ld-js
that referenced
this issue
Feb 9, 2022
gsvarovsky
added a commit
that referenced
this issue
Feb 9, 2022
Refinements to design Mindmap images
gsvarovsky
added a commit
to m-ld/m-ld-js
that referenced
this issue
Feb 17, 2022
gsvarovsky
added a commit
to m-ld/m-ld-spec
that referenced
this issue
Feb 19, 2022
m-ld/m-ld-security-spec#3: Unauthorised error
gsvarovsky
added a commit
that referenced
this issue
Mar 25, 2022
gsvarovsky
added a commit
that referenced
this issue
Jul 24, 2022
gsvarovsky
added a commit
to m-ld/m-ld-js
that referenced
this issue
Jul 26, 2022
gsvarovsky
added a commit
to m-ld/m-ld-js
that referenced
this issue
Jul 26, 2022
gsvarovsky
added a commit
that referenced
this issue
Jul 26, 2022
gsvarovsky
added a commit
to m-ld/timeld
that referenced
this issue
Aug 5, 2022
…s/devices and gateway, plus signing (WIP)
Merged
gsvarovsky
added a commit
to m-ld/timeld
that referenced
this issue
Aug 5, 2022
gsvarovsky
added a commit
to m-ld/timeld
that referenced
this issue
Aug 6, 2022
gsvarovsky
added a commit
that referenced
this issue
Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prototype integration of the controls into m-ld, and verification of the threat mitigation with tests. Engineering will proceed with tests and implementation combined. The intention of the prototyping is to validate the design, in terms of implementation complexity and against tests, not to deliver a production-ready implementation.
integrity
Whole domain authorisation to fixed user. It will be possible for an app to register the current user identity with the clone, and have the clone allow or prevent write access to the whole domain based on some hard-coded information. This is not a useful function by itself, but establishes the necessary framework for the following goals, and can be verified.
Whole domain authorisation m-ld-js#85
Data-driven authorisation. It will be possible to have the clone allow or prevent write access to sub-parts of the domain data, based on access control data in the domain. The available configuration complexity will be sufficient to show that it is possible to meet the requirements established in the threat models.
Data-driven authorisation m-ld-js#94
Externally-driven authorisation. It will be possible to have the clone allow or prevent write access to sub-parts of the domain, based on a configured protocol that is external to the domain data. One such protocol will be demonstrated.
Added statute "prover" extension loading via "extension subjects" m-ld-js#98
m-ld/m-ld-iroha: [Experimental] m-ld extensions using Iroha
traceability
Journal API. In order to verify traceability, it must be possible to access the clone journal (for example, to cryptographically verify signatures; implementing such signatures is the next goal).
#3: Journal API prototype #13
Signed journal entries. This is the ability to cryptographically bind the user identity and timestamp to write operations in the domain, such that their actions can be traced (and not repudiated).
Edge timeld#50
The text was updated successfully, but these errors were encountered: