Proof for a creation date

[Quan Zhou]

so GnuPG's timestamping isn't an option for this?
Even X509 has a timestamping feature for this kind of use.

On Fri, Dec 2, 2016 at 11:59 AM, Schlacta, Christ <aarcane at aarcane.org>
wrote:

> The easiest way is to publish your code to a publicly controlled source
> with a signature on or before your desired date. Not sure if there's a
> *better* way.
>
> On Dec 1, 2016 7:43 PM, "Bertram Scharpf" <lists at bertram-scharpf.de>
> wrote:
>
>> Hi,
>>
>> we all know that kidnappers do publish a picture of their
>> hostage holding up a todays newpaper. The purpose of this is
>> to proof that the victim was alive _after_ a certain point
>> of time. I want to do the opposite. I want to make evidence
>> that I created a document _before_ a certain point of time.
>>
>> I could use self-darkening ink but that won't be reflected
>> in a JPEG scan and my pen won't make the job that TeX does.
>> I could sign a newspapers home page but that cannot be
>> reproduced at a later point of time to verify the signature.
>>
>> Is there a standard way in GnuPG and in the keyholder
>> infrastructure to accomplish this task?
>>
>> Thanks in advance.
>>
>> Bertram
>>
>>
>> --
>> Bertram Scharpf
>> Stuttgart, Deutschland/Germany
>> http://www.bertram-scharpf.de
>>
>> _______________________________________________
>> Gnupg-users mailing list
>> Gnupg-users at gnupg.org
>> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>>
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>
>


-- 
Regards,

Quan Zhou
+------------------------+
|pub [expires 2019-05-04]|
|D7CF DCE8 2EBA 2766 499A|
|20DF 8273 6C6F ABCD 0A0F|
+------------------------+
|pub [revoked 2016-04-16]|
|44D2 0307 1643 E80F 2E31|
|F081 FAFA 6643 7F9F D46F|
+------------------------+
|quanzhou822 at gmail.com   |
|https://keybase.io/qzhou|
+------------------------+
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20161202/00c2e6ea/attachment.html>