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

From Robert Haas
Subject Re: Mail thread references in commits
Date
Msg-id CA+TgmoabrGK9M=ztjguTN6BCcpHDScJ-PDJ6BbDAoXdpUzrcHg@mail.gmail.com
Whole thread Raw
In response to Re: Mail thread references in commits  (Greg Stark <stark@mit.edu>)
Responses Re: Mail thread references in commits  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Nov 30, 2016 at 1:50 PM, Greg Stark <stark@mit.edu> wrote:
> 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...

...or the name of your company/your email hosting provider's company...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel safety of CURRENT_* family
Next
From: Robert Haas
Date:
Subject: Re: Broken SSL tests in master