issues
search
decentralized-identity
/
confidential-storage
Confidential Storage Specification and Implementation
https://identity.foundation/confidential-storage/
Apache License 2.0
78
stars
23
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Introduction: words that should appear (in context) in the Introduction
#192
mwherman2000
opened
3 years ago
0
"Confidential Storage Specification" is too general a title for this specification
#191
mwherman2000
opened
3 years ago
0
Security First Design Principle: what/how should the EDV architecture/design/implementation take into account specifically wrt to viruses and other malware? [Placefolder]
#190
mwherman2000
opened
3 years ago
0
Heterogeneous Multi-Vault/Server Instance Support
#189
mwherman2000
opened
3 years ago
0
Trust Levels for Content: Plain Text vs. Encrypted, Signed vs. Unsigned, vs. Not Resolvable: taxonomy proposal for EDV content resources
#188
mwherman2000
opened
3 years ago
14
"Directory" resource schema: needed to enable the CRUD of folders and subfolders of resources [Placeholder]
#187
mwherman2000
opened
3 years ago
2
Secure Logging: logging of all operations/transactions is a critical requirement for secure data stores [Business Requirement]
#186
mwherman2000
opened
3 years ago
8
Is it the intent of the Specification to adhere/support to any formal information security classification standards? ...America/International?
#185
mwherman2000
opened
3 years ago
1
Relevant Research Reports
#182
mwherman2000
opened
3 years ago
1
"EDV Microkernel" Architecture: C-callable "kernel" on which everything else is implemented (i.e. all of the services)
#181
mwherman2000
opened
3 years ago
1
"Protocols" should be its own top-level section in the specification
#180
mwherman2000
opened
3 years ago
2
"Services" should be it's own top-level section in the specification
#179
mwherman2000
opened
3 years ago
2
5.2.2 Creating a data vault - should be able to create a data vault with a simple C-callable API call (and optionally, using the HTTP protocol)
#178
mwherman2000
opened
3 years ago
0
5.2.1 Discovering Service Endpoints - this seemed to jump out of "nowhere"
#177
mwherman2000
opened
3 years ago
2
Multi-Resource/Multi-Vault/Multi-Server Instance ACID Transaction Scopes: scope statement to be added to the Spec
#176
mwherman2000
opened
3 years ago
3
1.3.3 Identifiers: just for entities (as defined in the spec) or ...
#174
mwherman2000
opened
3 years ago
0
Multi-Vault/Multi-Server Deployment Model: Can an [EDV server] instance (as defined in the spec) optionally simultaneously support more than one physical data vault?
#173
mwherman2000
opened
3 years ago
1
3.5 Operations: classic set of 4 CRUD operations insufficient. Use CARUMDRIGF
#172
mwherman2000
opened
3 years ago
6
Definition of full-sync replication is problematic/doesn't scale
#171
mwherman2000
opened
3 years ago
0
For a secure solution, bidirectional replication should be defined as two separate unidirectional connections
#170
mwherman2000
opened
3 years ago
0
Definition of instance is problematic
#169
mwherman2000
opened
3 years ago
0
1.4.1 Layered and modular architecture
#168
mwherman2000
opened
3 years ago
0
1.3.6 Protocols - default should be a "C callable API" not, for example, HTTP
#167
mwherman2000
opened
3 years ago
3
Content Versioning and Content Replication are two different animals
#166
mwherman2000
opened
3 years ago
0
Will there be one or two Confidential Storage specifications?
#165
agropper
opened
3 years ago
11
Replication questions
#162
tahpot
opened
3 years ago
5
What is the overarching glossary for the terms that are used in this specification?
#159
mwherman2000
opened
3 years ago
0
What are "Encrypted Datastores"?
#158
mwherman2000
opened
3 years ago
0
PROPOSAL: Anyone with the link has the capability to access the resource
#157
OR13
closed
3 years ago
0
Add Example Encrypted Data Vault Server
#156
OR13
closed
3 years ago
0
date correction
#154
nembal
closed
3 years ago
0
API Neutrality as a Human Right and two proposals
#152
agropper
opened
3 years ago
0
Add option to get full documents from queries
#151
DRK3
opened
3 years ago
10
Bump ini from 1.3.5 to 1.3.8 in /packages/vendor-interoperability
#146
dependabot[bot]
closed
3 years ago
0
Fix query URL examples.
#145
dmitrizagidulin
closed
3 years ago
0
Add id property to example EDV Configuration object.
#144
dmitrizagidulin
closed
3 years ago
0
Add example authorization capabilities for operations.
#142
dmitrizagidulin
closed
2 years ago
1
Add a GNAP authorization request and a ZCAP response for the operations in the spec
#141
dlongley
opened
3 years ago
1
Add Operations section to Concepts.
#140
dmitrizagidulin
closed
3 years ago
0
Add Aries Framework Go to Vendor Interoperability Tests
#139
OR13
opened
3 years ago
1
Define authorization structure and invocation for hubs and edvs
#136
OR13
closed
3 years ago
0
PROPOSAL: HTTP Signatures MUST be supported for invocations of authorization by EDVs and Hubs.
#135
OR13
opened
3 years ago
0
PROPOSAL: Authorization Scopes MUST be expressed as ZCAPs encoded as GNAP Structured Scopes
#134
OR13
opened
3 years ago
1
Rename Spec
#132
OR13
closed
3 years ago
0
Will EDV and ADV protocols co-exist at the same layer?
#131
agropper
opened
3 years ago
21
editorial fixes
#129
OR13
closed
3 years ago
1
Delete This Issue Once this Appendix has been merged into the identity hubs section
#128
OR13
opened
3 years ago
3
Help Review the DID Use Cases Human Narrative
#127
OR13
opened
3 years ago
0
Spec Versioning and Stability of Dependencies
#126
OR13
opened
3 years ago
1
HTTP Signature APIs have been reworked to support HTTP Structured Headers
#125
OR13
opened
3 years ago
0
Previous
Next