On Tue, Jun 20, 2017 at 4:48 PM, Richard Hipp wrote:
> Review and criticism of this change is welcomed.
>
Is an artificial stack limit really necessary? i can't personally conceive
of any attacks which could cause fossil to recurse unduly (but i'm also
someone uncreative when it comes to attack
On Jun 20, 2017, at 8:48 AM, Richard Hipp wrote:
>
> Review and criticism of this change is welcomed.
Since updating and installing it, I’m getting occasional aborts in relatively
simple tasks like fossil diff and fossil checkin.
fossil diff with uncommitted changes doesn’t give any diagnostic
The patch at https://www.fossil-scm.org/fossil/info/6e6e4b1d26e187ed
attempts to limit the amount of heap space and stack space used by
Fossil as a defense against the "stack clash" bug found on many
versions of Unix. There are no known attacks against Fossil using
stack clash. This is a proactiv
