Hi Prasanth, thanks for reaching out. And thanks Tio and Adam for
chiming in with very helpful replies. You are right - this should
definitely be documented somewhere more prominently. Currently there
is some sample output documented as part of the server API here -
https://github.com/danwent/Perspectives-Server/blob/master/doc/api.md
, but we should perhaps add it to the Help page and have it online.
Adam and Tio are correct - the 'fp' stands for 'fingerprint', and that
field is a hash of the website's certificate seen by a notary.
Currently the notaries only look at the 'main' end-entity or leaf
certificate for a site. This is something we would like to address in
the future - collecting data on other certificates such as resources
from a different domain[1].
As also mentioned the timestamp is a unix timestamp. The 'start'
timestamp is the first time that a notary saw the given certificate
for that site, and continued seeing it up until the 'end' timestamp.
The "sig" field is a cryptographic signature of the message the notary
sends. It is indeed created using a notary's secret key, so it can be
verified and validated by your Perspectives plugin in the browser.
Does that make sense?
As Adam points out, the fingerprints/hashes are unfortunately still
using the MD5 algorithm. We definitely want to upgrade this to SHA256;
it is on our list of priorities in the Perspectives Roadmap[2].
I hope that helps. Thanks for your interest in the project!
[1]
https://github.com/danwent/Perspectives/issues/14
[2]
https://github.com/danwent/Perspectives/wiki/Perspectives-Roadmap