Quote from: pine on July 28, 2012, 02:13 amAnd don't forget to sign DPR's public key before verifying a signed message by him folks.I won't be doing that until he starts exhibiting greater OpenPGP understanding. See my response to his backup URL threads where I verified the signature.Quote from: pine on July 28, 2012, 02:13 amA thought on more sophisticated PGP tech beyond simply knowing how to encrypt and decrypt.Is it possible to create a PGP encrypted message that is designed be Timestamp sensitive?You'd need to create your own OpenPGP implementation. It may be possible to write the relevant code as an extension to GPG.Quote from: pine on July 28, 2012, 02:13 amNow, I know what you're going to say: the PGP software needs to know the time... And that you could always simply change the clock on your computer to suit yourself.However, imagine a bunch of servers that exist to tell you the time, they already exist. Now, what if those servers were arranged into a web of trust network communicating the Timestamp with your PGP software via signed encrypted messaging?The function would need to be aware of NTP servers and maintain connections to them in order to decrypt the messages that are encrypted this way. It may also require these connections when encrypting data. Some users may then be unable to perform those functions if their threat assessment requires encryption and decryption be performed offline. So it would have to be optional.There have been PGP timestamp services where a message (usually encrypted) would be sent to another server which signs the message to provide an independently verifiable timestamp of when the message was created. That's solely for verification of file creation and does not provide the kind of functions you described.