Problem with faked-system-time option

[MFPA]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi


On Thursday 16 June 2011 at 6:32:34 AM, in
<mid:BANLkTinxDzveGfrwDn82ub+Y46MknTMW4Q at mail.gmail.com>, Jerome Baum
wrote:


> As for the error/resolution notation, someone else
> (can't recall who and the gmail thread is unbearable)
> mentioned that this would be relevant, and with the
> same breath that you could state this in your signing
> policy. My thought process is, what if I have two
> machines, and one is NTP-synced (or even takes legal
> time from the broadcast signal) while the other
> regularly drifts up to 10 minutes, or runs timestamping
> in batches, etc.

> Of course, I could set up separate keys. Personally I'd
> opt for the notation, as that's also computer-readable
> (think "Good timestamp from Alice, between 10:00 and
> 11:00 on 2011-06-16"

Excuse the pedantry but how do we get "between 10:00 and 11:00"
reliably from a clock that regularly drifts up to 10 minutes?


- --
Best regards

MFPA                    mailto:expires2011 at ymail.com

Don't cry because it is over - smile because it happened
-----BEGIN PGP SIGNATURE-----

iQE7BAEBCgClBQJN+6B7nhSAAAAAAEAAVXNpZ25pbmdfa2V5X0lEIHNpZ25pbmdf
a2V5X0ZpbmdlcnByaW50IEAgIE1hc3Rlcl9rZXlfRmluZ2VycHJpbnQgQThBOTBC
OEVBRDBDNkU2OSBCQTIzOUI0NjgxRjFFRjk1MThFNkJENDY0NDdFQ0EwMyBAIEJB
MjM5QjQ2ODFGMUVGOTUxOEU2QkQ0NjQ0N0VDQTAzAAoJEKipC46tDG5pctgEALZA
wadWGwVeFDGbjWgWIbmE4imLj2dSa/MhJMVVPf+towmalJWmxdIk3d+rkeP70mb7
lKelvAWCY7UUUayVbfgaOtsvFpKjhX+DqjJqtxaXaKcm+Iu6R2M8r2TzHlpwNqr7
WfFK7eLhKuvv8vrMujCerpVihG+efVHd0DpuSuto
=qj3t
-----END PGP SIGNATURE-----