Skip to main content

Private Messaging In Public Forums

We have introduced private messaging over public forums in Certisfy, ie you can create and post encrypted messages in public(online) forums via Certisfy private message links. 


You can also add a Certisfy link to your profile (or an appropriate place such as a web page) that will allow someone clicking on it to create a message that can be encrypted and sent/posted where appropriate.


To allow others to encrypt messages for you, you'll first have to create a certificate if you don't already have one. Then copy an encryption URL from the certificate that you then share with others who may want to send/post a private message to you.

In cases where a private message link is via an non-trusted source (internet at large), it is best to link private messaging to verified IDs (could be anonymous), that way a user can be sure their private message is going to the expected party. 

This ability is supported by allowing users to trigger the message encryption from a verification screen, meaning they'll encrypt with the certificate associated with the verification.


Private messaging via Certisfy is not breaking new ground in terms of the ability to easily take advantage of private messaging using public key cryptography, but it is a neat enhancement that Certisfy users will find useful. The ability to link private messaging to trusted recipients is also something that adds value.

Here's a demo showing how to use the feature:





 

Comments

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...

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...

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} , ...