Tamper-Evident Logs
transparency.dev
Tamper-Evident Logs
1–10 of 51 posts
Re: Tamper-Evident Logs
#2We built a tamper evident log system for https content. The beta is over here: https://www.transparencylog.com/
Or try out the CLI tool https://github.com/transparencylog/tl#installation
Re: Tamper-Evident Logs
#3Couldn't we use, you know, git for the many applications that require a verifiable history of commits but don't need to be super fast or real-time?
Re: Tamper-Evident Logs
#4RFC 5848, "Signed Syslog Messages":
> This document describes a mechanism to add origin authentication, message integrity, replay resistance, message sequencing, and detection of missing messages to the transmitted syslog messages. This specification is intended to be used in conjunction with the work defined in RFC 5424, "The Syslog Protocol".
Re: Tamper-Evident Logs
#5Sorry I read the page and I found it very vague.
Pretty graphics and lot of white space for not much meat.
Basically, looks like the command pattern implemented with signed token for every time you read, you must mutate the 'chain' or array of information. Am I close?
Re: Tamper-Evident Logs
#6Couldn't we use, you know, git for the many applications that require a verifiable history of commits but don't need to be super fast or real-time?
"Don't be snarky."
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
https://news.ycombinator.com/newsguidelines.html
You may have a good point, but for it to be a good comment you would need to drop the snark and engage more specifically with the details of the article. The odds, for example, that the authors don't know about or have thought about git are basically zero.
Re: Tamper-Evident Logs
#7I’m sorry, but Trillian? That seems like a pretty major name collision with a well known piece of software that has been around for decades and has zero chance of getting displaced in search rankings lol
Re: Tamper-Evident Logs
#8Maybe I'm missing something, but there is already the term "append only logs" which we use everywhere. How is this different from append only logs? Append only logs rely on cryptography to make the history transparent too. I skimmed through the website but couldn't find a distinction.
Also, the website format is kinda weird. As I reach the bottom of the page, it looks like this is a promotional site for Trillian. Maybe the confusion comes from here. What is this site really about?
Re: Tamper-Evident Logs
#9I’m sorry, but Trillian? That seems like a pretty major name collision with a well known piece of software that has been around for decades and has zero chance of getting displaced in search rankings lol
> has zero chance of getting displaced in search rankings
unless this new product happens to be run by a company that controls a prominent search ranking algorithm
Re: Tamper-Evident Logs
#10Maybe I'm missing something, but there is already the term "append only logs" which we use everywhere. How is this different from append only logs? Append only logs rely on cryptography to make the history transparent too. I skimmed through the website but couldn't find a distinction. Also, the website format is kinda weird. As I reach the bottom of the page, it looks like this is a promotional site for Trillian. May…
What cryptography are you referring to when talking about append-only logs? To me, an AOL is just a list of records that has a single operation, append. It could be implemented as a file that is only opened in append mode, multiple files (eg logrotate), a lib that works in memory, a process that exposes an API, etc. I don't see any cryptography here.