Difference between revisions of "Did:orb"

From MgmtWiki
Jump to: navigation, search
(Software Bill of Materials)
(Server Purposes)
Line 28: Line 28:
===Server Purposes===
===Server Purposes===
The current means to understand did:orb are:
The current means to understand did:orb base install. (not to be confused with a leaf node with about 1/2 of these servers)
{|border="1" padding="2" width="1111px"
{|border="1" padding="2" width="1111px"
|      Image          || Command        ||  Ports  ||  Names
|      Image          || Command        ||  Ports  ||  Names

Revision as of 16:26, 13 June 2021

Full Title

Description of the did:orb method implementation.


still working on the implementation. I can let you know once we have the basics ready.


The current means to understand implemented servers are:

Term Purpose or Behavior
claim An assertion made about a subject. (This can only be considered true if the term subject is interpreted very broadly.)
subject A thing about which claims are made.(Complete circulate - no real meaning at all.)
user agent A program, such as a browser or other Web client, that mediates the communication between holders, issuers, and verifiers. (This does not match DID core well at all.)
validation The assurance that a verifiable credential or a verifiable presentation meets the needs of a verifier and other dependent stakeholders.
vct Verifiable Credential Transparency

The Implementation

Server Purposes

The current means to understand did:orb base install. (not to be confused with a leaf node with about 1/2 of these servers)

Image Command Ports Names
ghcr.io/trustbloc/orb:latest "/usr/bin/orb start">443/tcp orb2.domain1.com
ghcr.io/trustbloc/orb:latest "/usr/bin/orb start">443/tcp orb.domain2.com
ghcr.io/trustbloc/orb:latest "/usr/bin/orb start">443/tcp orb.domain1.com
ghcr.io/trustbloc/orb:latest "/usr/bin/orb start">443/tcp orb.domain3.com
ghcr.io/trustbloc-cicd/kms:0.1.7-snapshot-bff24d1 "/bin/sh -c 'kms-res…">7878/tcp orb.kms
gcr.io/trillian-opensource-ci/log_signer:eac... "/trillian_log_signe…">8091/tcp orb.trillian.log.signer
gcr.io/trillian-opensource-ci/log_server:eac... "/trillian_log_serve…">8090/tcp orb.trillian.log.server
couchdb:3.1.0 "tini -- /docker-ent…" 4369/tcp,9100/tcp,>5984/tcp couchdb.shared.com
couchdb:3.1.0 "tini -- /docker-ent…" 4369/tcp,9100/tcp,>5984/tcp couchdb.kms.com
mysql:8.0.24 "docker-entrypoint.s…">3306/tcp, 33060/tcp orb.mysql
ghcr.io/trustbloc/vct:v0.1.0 "/usr/bin/vct start">8077/tcp orb.vct
ipfs/go-ipfs:master-2021-04-22-eea198f "/sbin/tini -- /usr/…" 4001/tcp, 8080-8081/tcp, 4001/udp,>5001/tcp ipfs


Troy Ronda (SecureKey) 2021-05-04

In other news, we also pushed the first pre-release 0.1 version of vct and orb. It’s still early days - this is really a pre-release focused on early integration.


We’ll soon bring up a third dev domain so we can start seeing announcements.

Notice the canonical ID for that DID example above: 


Did not run because go version files.

  • Remove all GO and reinstall 1.16.3

then add these to ~/.profile

export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH
  • Makefile is using abspath in call to frapsoft/openssl with is two unacknowledged dependencies in did:orb code.

Software Bill of Materials

In response to Executive Order on Cybersecurity these are the components that were required to build the product. It is not clear which parts actually provide code to the finished product, but they all contributed to the building of the finished product. Where finished product includes the certificates and other support files.

  • Ubuntu 20.04
  • sudo apt update - on 21-05-13 this installed 20 updates just in the past one month including many libraries as well as python3
  • GoLang 1.16.3
  • frapsoft/openssl
  • Docker
  • Docker-compose (both from docker-desktop)