On Wed, Aug 29, 2012 at 7:58 AM, Martijn Coppoolse < [email protected]> wrote:
> How is the contact info garbled? I assume it’s being encrypted using some > other ticket-related info, but I can't figure out why it would decrypt to > something else here... To my surprise, it seems that the contact info field is indeed munged... >From the main repo: sqlite> select distinct(private_contact) from ticket; <SNIP 1 clear-text address> 6b3f5a8f6def0ef153f7a89fb5a1b0fa01d7509e 63f4cb9d6971f7dbdee05412b8546975182b32e4 24b67375dd2ec6c7381a5ad34cfcf006f0b9c260 ... Which i see referenced here in rebuild.c: @ -- Some ticket content (such as the originators email address or contact @ -- information) needs to be obscured to protect privacy. This is achieved @ -- by storing an SHA1 hash of the content. For display, the hash is @ -- mapped back into the original text using this table. @ -- @ -- This table contains sensitive information and should not be shared @ -- with unauthorized users. @ -- @ CREATE TABLE IF NOT EXISTS concealed( @ hash TEXT PRIMARY KEY, -- The SHA1 hash of content @ mtime INTEGER, -- Time created. Seconds since 1970 @ content TEXT -- Content intended to be concealed @ ); can you try running rebuild? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
