#dpki — Public Fediverse posts

@atomicpoet @youid Here's an explainer post I published recently about this most important approach to #Identity #Authenticity that scales across the #Internet, #Web, and #Fediverse.

https://community.openlinksw.com/t/howto-using-chat-gpt-to-generate-a-sequence-diagram-knowledge-graph-about-the-tls-protocol-using-chat-gpt/3798

#TLS #HTTPS #NetIDTLS #TLS #PKI #DPKI #NetID #WebID #YouID #SSI

#Identity #Authenticity, remains a HUGE problem at the #Internet->#Web->#SocialMedia levels. It's so big that it has trivially imploded #Twitter via the recent Blue Checkmark/Badge disaster.

A #SemanticWeb solves this headache, once understood, by way of #TLS integration using a #Hyperlink -- as demonstrated by protocol extensions such as #NetIDTLS and #WebIDTLS.

Here's a post that includes a NetIDTLS Sequence Flow Diagram to aid understanding.

https://community.openlinksw.com/t/howto-using-chat-gpt-to-generate-a-sequence-diagram-knowledge-graph-about-the-tls-protocol-using-chat-gpt/3798#netidtls-a-tls-cca-extension-1

#LinkedData #DPKI

How verifiable credentials generated by @youid enable self-sovereign identity (#SSI): a user-controlled approach to #identity, via #HTTPS session initialization using Client Certificate Authentication (CCA).

Watch: https://youtu.be/n6DZeqcqkwM

Adding this as an identity verification option, alongside "rel=me", enhances user #privacy and identity authenticity across the #Fediverse.

/cc @openlink @youid @atomicpoet @judell @Mastodon @evan

#DPKI #LinkedData #NetID #NetIDTLS #Screencast

@openlink @youid @atomicpoet @judell,

By more.. I mean:

The Link In Bio profile document generation is going to get a lot easier i.e., cross-references to other profile pages will be handled via the @youid credentials capturing form; and this is restricted to an arbitrary number i.e., you can provide more than 4 cross-references if so required.

#Identity #Authenticity #SSI #X509 #DPKI #NetID #NetIDTLS

@openlink @youid Wonderful!

What is this about?

User-controlled self-sovereign #identity (#SSI) that scales to both the #Internet & #Web.

@youid generates:

[1] Public & Private Credentials that can be reconciled as part of an extended #TLS handshake

[2] An #HTML-based profile doc comprising verifiable credentials -- what's also referred to as a Link In Bio doc

More to come..

/cc @atomicpoet @judell

#YouID #NetID #NetIDTLS #Privacy #RWW #X509 #WebID #PKI #DPKI

@bertrand ,

#Identity #Authenticity demo using #DPKI:

[1] https://kingsley.idehen.net/public_home/kidehen/Public/YouID/public-credentials-1/index.html -- profile document comprising credentials

[2] https://tinyurl.com/376bncdc -- credentials verification via a #NetIDTLS server equipped with an extended #TLS handshake that de-references #hyperlink used in #X509 cert en route to credentials reconciliation

[3] https://kingsley.idehen.net/public_home/kidehen/Public/YouID/public-credentials-1/ -- artifacts from my #ODSBriefcase folder

/cc @meneer @aniltj @w3c @atomicpoet

#NetID #YouID #VerifiableCredentials #SSI

@meneer,

To be clear, I am a firm believer in loosely-coupling the following:

1. #Identity -- via identifiers (e.g., a #hyperlink)
2. #Identification -- via credentials (graph)
3. #authentication -- using various protocols
4. #authorization -- access controls (eg #ABAC)
5. #storage -- file systems or #DBMS

When I speak about #DPKI and #ZeroTrust the focal points are 1-3.

#HTTP offers abstraction atop the #Internet that deemphasizes #DNS re entity naming.

/cc @bertrand @aniltj @w3c

@meneer,

An individual doesn't need a CA in the mix to attain trust, that's required on the backend if you are providing e-commerce (e.g., Amazon.com etc).

An individual can use a #ZeroTrust algorithm as the basis for establishing trust with family, groups etc..

That's what #DPKI solves for, via #X509, #TLS, and machine-computable entity relationship type semantics.

These issues have been deeply thought through over the years. 😀

/cc @aniltj @w3c

#NetID #YouID #NetIDTLS

@aniltj,

#LinkedData is essential to user-controlled #Identity #Authenticity and #Privacy.

I can demonstrate that with ease, and debate (with live examples) any #BigTech vendor rep that would like to covertly claim otherwise.

#DPKI is real, and it works for users seeking full control over their identity and privacy. It doesn't work for vendors seeking to exploit users covertly via the "bit of privacy" approach!

/cc @atomicpoet @Mastodon @youid

#NetID #YouID #NetIDTLS #TLS #WebID

@eb,

Yes!

Look at what it has enabled so far, courtesy of its connectivity prowess:

1. Global Web of Documents that unshackles access to documents from machine and operating system silos

2. Global #DataSpaces that bring sociality to the digital realm

And there is so much more to come re:

1. self-sovereign identity (#ssi)

2. #identity #authenticity via #dpki

3. #privacy

4. data integration via Knowledge Graphs

#Web #SemanticWeb #LinkedData #DataConnectivity #KnowledgeGraph #Web30

@ben ,
It isn’t more complicated if there’s a user-friendly solution delivered as an app or browser extension for:

1. Generating Certificate

2. Extracting #PublicKey hash in copy & paste friendly form

3. Packaging credentials in a #PKCS12 file (understood by all modern operating systems)

That’s exactly what our #YouID browser extension offers 😀

/cc @Mastodon

#DPKI #NetID #WebID #X509 #TLS #Identity #Authenticity

@acjay,

Yes, the #Fediverse and #Web at large.

#Identity #Authenticity can be handled using existing open standards; it just needs new thinking on the parts of both end-users and solution providers.

If you lookup any of the following tags you will see related posts on this important self-sovereign (#SSI) matter: #YouID, #NetID, or #WebID, or #DPKI.

#X509 #TLS #HTTPS