[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Home]
Board
Settings Home
/g/ - Technology



Thread archived.
You cannot reply anymore.




File: Brett Kavanaugh Angry.jpg (190 KB, 1280x853)
190 KB
190 KB JPG
Hello anons,
I am considering developing a FOSS trusted timestamp software, but I'm a bit hung up on how exactly I should go about allowing offline timestamping. Although using third party services (such as the btc blockchain or cert servers) would be a part of the software, I don't want to have to always rely on a remote server or stable internet access.
So far, I have looked at methods in ANSI X9.95 like hash linking...

Is there anything else out there that I could use?
>>
>>69317644

What exactly are you building? Depending on that, there might be some "escapes" you can use to get a trusted timestamp.

There is that notary system that Kaminsky developed as a HTTPS security root. Could it be reused?
>>
>>69318356
I'm looking to make it a general API for use with files or text strings (such as entries in a log file). Potential use cases that I'm thinking about at the moment are recording GPS data, or having records to prove possession of data at a specific time.

As for the language, I'm thinking of C++ for the client software. I want it to be able to run on something like a smart watch, for example, but still be usable on more traditional devices.
>>
>>69317644
Who is the shithead attempted rapist?
>>
File: filename.png (9 KB, 541x212)
9 KB
9 KB PNG
>>69319670
What are you talking about? Are you referring to the OP image?
>>
>>69317644
what do you need a 'tim' stamp for?



Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.