Thus said Richard Hipp on Fri, 11 Aug 2017 11:41:09 -0400:
> I don't feel a particular need to rush out a new release containing
> this fix. But I am open to arguments to the contrary, if you feel
> differently.
I think at a certain point, users of any software have to take their
own
On 8/12/17, Andy Bradford wrote:
> I think a bigger problem that Fossil has is partially addressed here:
>
> http://www.fossil-scm.org/index.html/info/ce7baa9798de21aa
>
> which is similar to the attack vector that you just fixed, though
> perhaps worse because it allows remote execution of
On 8/12/17, Richard Hipp wrote:
>
> I went a slightly different route...
Having thought about this more, I'm thinking now that I might go back
to Andy's approach
--
D. Richard Hipp
d...@sqlite.org
___
fossil-dev mailing list
fossil-dev@mailinglist
