Skip to main content

The dubiousness of digitized signature services

Notice I referred to "digitized" instead of digital, this is a very important distinction. These services essentially offer ways to transport handwritten scribbles into digital processes. They can be anything from attaching a Microsoft paint scribble or a scan of one written on a piece of paper, to custom font generation that makes  your signature look like you are a former president of the united states.

I wont mention any such services by name but if you've purchased a house or engaged in any sort of contract paperwork activity (leases..etc) you have likely encountered these services. Last I checked, one of these companies is worth north of $40B, no doubt reflecting the size of the market for such services.


First, what is the purpose of any signature? as the name suggests, it is primarily to ascribe provenance to something, be it an abstract thing such as a legal agreement expressed in writing or a physical object such as a painting. We also use the notion of signature to refer to a manifestation that serves as a tell-tale sign of some fact (or the truthfulness thereof) without necessarily observing the actual manifestation of the fact itself.

What is the purpose of signing a paper then? Well, it is suppose to first, attest to the fact that the entity whose identity is associated with the document is consenting to whatever it is that the paper implies. Second, your scribbles are supposed to be unique, such that someone could not forge them and fool others into accepting an agreement that the identified entity is in fact not a party to.


Hand written signatures even in the days of king Henry were more of an intellectual pretense than an effective mechanism for genuine projection of trust. That they have persisted into the 21st century is more than distressing.

We now have even the democratic franchise of voting citizens tethered to matching variations of such scribbles. My handwritten signature varies based on what I had for breakfast, so the idea that anyone would want to judge the authenticity of any document based on it would be hilarious if it weren't such a serious matter.

The entire edifice of affixing handwritten scribbles (or their digital imitations) to documents is quite mindless if the aim of signatures as described above is to be achieved.


Obviously the need for entities to affirmatively agree to conditions and to have that recorded in a way that is tamper-proof and indisputable has not gone away. However, given the purpose of signatures, it is clear that scribbles on paper or their digitized cousins are certainly not an answer. At best one can consider these services as ceremonial, in as far as they facilitate the continuation of the pre-digital processes that demand handwritten signatures.


What then is the solution to signatures in the digital era? The answer is simple and well understood (hard to believe perhaps), PKI certificates. Given that Certisfy is about leveraging PKI for trust on the internet, this is a self-serving answer but it is also a true answer.

A digital signature (not a digitized one) of a document, along with the certificate whose private key was used to generate such a signature is all that is needed to achieve the intended goal of handwritten signatures.

From a purely technical requirement perspective, you would need to add no more than two new entries to your data model to support this, a field to store the cryptographic signature and a field to store the cryptographic certificate-chain that can verify that signature. If a dispute were to emerge a century from now, you wouldn't need to hire medieval forensic experts to authenticate the document, you would simply run the signature and document through the appropriate cryptographic verification function to authenticate it.

There are of course legitimate arguments to make against PKI (some favor blockchain contracts..etc), but when the alternative is handwritten scribbles, such arguments diminish towards meaninglessness.

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

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

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