Mercurial > p > roundup > code
view website/issues/extensions/timestamp.py @ 7697:c73a1177c2b2
fix: roundup-demo, interactive mode would nuke an existing tracker.
Tonu Mikk demonstrated a bug in roundup-demo. When invoked without a
tracker home on the command line, it would nuke an existing directory
specified interactively.
There is still a minor bug. If an invalid home directory is specified,
roundup-demo will prompt for the template to use before reporting:
Error: Refusing to nuke non-tracker directory:
but this doesn't cause data loss so not worth fixing at this time.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 08 Nov 2023 21:18:34 -0500 |
| parents | 35ea9b1efc14 |
| children |
line wrap: on
line source
import time, struct, base64 from roundup.cgi.actions import RegisterAction from roundup.cgi.exceptions import * def timestamp(): return base64.encodestring(struct.pack("i", time.time())).strip() def unpack_timestamp(s): return struct.unpack("i",base64.decodestring(s))[0] class Timestamped: def check(self): try: created = unpack_timestamp(self.form['opaque'].value) except KeyError: raise FormError("somebody tampered with the form") if time.time() - created < 4: raise FormError("responding to the form too quickly") return True class TimestampedRegister(Timestamped, RegisterAction): def permission(self): self.check() RegisterAction.permission(self) def init(instance): instance.registerUtil('timestamp', timestamp) instance.registerAction('register', TimestampedRegister)
