This is an attempt to do a 'post-mortem' on XSA-283, to find out how
the error came about, and consider what changes we could make to code
/ processes to prevent such errors from happening in the future. The
Security Team hopes to make it a habit to perform such analyses in the
future.
As it happ
On Feb 25, 2019, at 10:14, George Dunlap wrote:
>
> This is an attempt to do a 'post-mortem' on XSA-283, to find out how
> the error came about, and consider what changes we could make to code
> / processes to prevent such errors from happening in the future. The
> Security Team hopes to make it
> On Feb 25, 2019, at 11:20 PM, Rich Persaud wrote:
>
> On Feb 25, 2019, at 10:14, George Dunlap wrote:
>>
>> This is an attempt to do a 'post-mortem' on XSA-283, to find out how
>> the error came about, and consider what changes we could make to code
>> / processes to prevent such errors fro
