Skip to main content

Build Your Own Trust Chain

We have added the ability to create custom trust chains in Certisfy that are verifiable independent of the Certisfy PKI root. These trust chains will lack the identity component of trustworthy Certisfy certificate so owners of such chains are responsible for implementing their own identity procedures.

Receivers of claims from such custom trust chains will have to whitelist (bookmark in Certisfy) the root certificate in order for claims from those certificates to pass verification. Use cases for custom trust chains are many.


Software package supply chain trust

There is currently an ongoing challenge around software supply chain security, ie developers integrate software libraries and components into their own applications and solutions are faced with the prospect of unwittingly including malicious vulnerabilities.

The problem ultimately boils down to the difficulty of ensuring the people who have write access to these packages are trustworthy. This would remain an ongoing problem requiring not just core due diligence by package owners and maintainers but the general ecosystem monitoring. Even after vetting a contributor, it is still possible they are malicious/compromised.

Another front related to this challenge has to do with AI instruction packages, ie packages such as agent skills. Packaging AI instructions via skills and distributing for general use is likely going to be a key way to scale AI utility by making it possible for more users to leverage the work of others. 

If one person has done the work of packaging instructions and supporting material (including code) for a given task, it makes sense to facilitate the re-use of that effort.

Distributed trust solutions via cryptographic trust chains are not a silver bullet but could certainly help a lot. 

In Certisfy, you can create certificates that support delegation and use that to implement your own trust chain. For instance any well-known and trusted entity/individual can create a root certificate and via delegation build a trust chain from that root. 

Each trust chain is free to institute its own rules/procedures for validating and issuing certificates. The Certisfy toolkit is flexible. Users can whitelist trusted roots both in Certisfy or through third-party SDK integrated solutions.

Git for instance supports verification for commits but that doesn't support any delegation mechanism by default. You can however use a key on a trusted chain for commits thus making that mechanism much more flexible, or embed your commit signing public key onto a trusted chain certificate. 

In other words a verifier can verify a git commit signature, then validate that the issuer of the signature is on a trust chain they trust.


Non-Technical Use cases

There are countless no-technical uses cases that follow a delegated authority approval structure that works well when implemented as a trust chain. These can be both long-run processes or short projects or just fun activities.


Nothing described above requires something like Certisfy, you can achieve some of the same things with openssl and a cli tool for instance, the Certisfy value prop at least in this context is UX, especially as it relates to trust delegation.

Here is a demo of how one use these capabilities:



 

Comments

Post a Comment

Popular posts from this blog

Trusted URLs Via Cryptographic Signatures

With Certisfy sticker functionality, ie the ability to publish cryptographic signatures as claims, users can share trusted URLs by leveraging the verification tied to trustworthy claims. URLs can be included in trustworthy claims and posted for anything for which a user wants to project trust. They can also be restricted to sources(ie referrer) so that the link can't be fraudulently reposted elsewhere. When you include links in a claim that you want to associate trust with, users will first be able to verify the link provider via the claim and then decide whether the link and associated information is trustworthy. In an AI saturated online space, there is significant value in a link/url being able to provide a strong signal of authenticity or trust. A trusted creator or a journalist can post links tied to a Certisfy verification as a means to project trust and expand reach. With verification links backed by high quality trust projection, we can have in essence a verified web. Here...
Post a Comment
Read more

Using .gov Email Addresses For Age And Information Verification

Over the years we've experimented with ideas that leverage what can be thought of as civic trust infrastructure to address trust related problems on the Internet.  Previously we created a browser extension and proxy service that allowed users to use access to their IRS  Get Transcript ONLINE  access as a way to procure trustworthy cryptographic ID certificates.  Essentially treating access to the Get Transcript ONLINE service as automatic ID verification and using that to issue (via a web proxy) ID certificates.  We also developed the trust relay protocol , a similar approach that leverages existing sources of trust as a means to address internet trust challenges. These experiments ultimately lead to the development of the Certisfy app and service. We have launched another significant experimental approach, leveraging .gov email addresses as a mechanism for bootstrapping a cryptographic trust chain . Think of this as a sort of  web of trust implementa...
Post a Comment
Read more

Using Keybase and PGP To Build Certificate Trust Chains

We are expanding our previous experiment to include people who posses PGP keys hosted at certain domains. For now we are whitelisting Keybase.io, meaning if you have a Keybase PGP key it can be used to procure a trust anchor certificate via the Certisfy app. It should be noted that this is strictly experimental, meaning most certificates will likely at some point be suspended or out right revoked if it seems they are being used to issue untrustworthy certificates.  The allowance of Keybase is not ideal since there is no id proofing and there is no reason to assume the person behind the Keybase key is a suitable trust anchor. It is however something used by folks interested in cryptographic solutions related to internet trust and security, so at least for experimentation it is appropriate. To validate a certificate request with your Keybase PGP key, first use your Keybase key to sign the following text (no trailing or leading spaces): Using public key hosted at ${PGPPubkeyURL} , ...
Post a Comment
Read more