Re: Mail thread references in commits - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Mail thread references in commits
Date
Msg-id CAM-w4HNY_h656VEAga88Sn0xHRPQNX23Nu455r+ySD4UFuopKg@mail.gmail.com
Whole thread Raw
In response to Re: Mail thread references in commits  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Mail thread references in commits  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 30 November 2016 at 16:19, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> https://www.postgresql.org/message-id/CAB7nPqTHyDYF-FO+fZvxRhz-7_hPTm4RodBcsy9-NoqHvEtc3w@mail.gmail.com
>
> I'll be interested to know if it breaks anyone's MUA. If it doesn't all we
> will be arguing about are aesthetics, and I'm a firm believer in function
> over form.

I can't say I feel especially strongly either way on this but just to
toss out a small thing that might make a small difference....

If you happen to know how your message-ids are generated then you
might be able to do something useful with them. For instance, you
could search all git commits for urls to messages you wrote -- for
instance any commit that has CAB7nPq is referencing a message written
by Michael Paquier.

On the other hand you could put something naughty in the message-id
forcing everyone else to use URLs with dirty words in them. Or with
words like "terrorist" in them. Or with some javascript/html injection
attack of some sort...

-- 
greg



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: EvalPlanQual() doesn't follow LockTuple() pattern
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Build HTML documentation using XSLT stylesheets by default