On Mon, Jan 15, 2018 at 11:27 AM, Richard Hipp wrote:
I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
> utility function. The fossil_pledge(X,Y) function is a macro that
> evaluates to a no-op except when compiled with -DFOSSIL_HAVE_PLEDGE.
> If the FOSSIL_HAVE_PLEDGE macr
Thus said Richard Hipp on Mon, 15 Jan 2018 11:27:20 -0500:
> I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
> utility function.
I've added a new branch called pledge-additions with additional pledge()
restrictions for the status command. We can continue to pledgify other
Thus said Richard Hipp on Mon, 15 Jan 2018 11:27:20 -0500:
> I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
> utility function. The fossil_pledge(X,Y) function is a macro that
> evaluates to a no-op except when compiled with -DFOSSIL_HAVE_PLEDGE.
> If the FOSSIL_HAVE
I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
utility function. The fossil_pledge(X,Y) function is a macro that
evaluates to a no-op except when compiled with -DFOSSIL_HAVE_PLEDGE.
If the FOSSIL_HAVE_PLEDGE macro is defined, then a routine is called
when invokes pledge() a
On 01/14/18 18:06, Richard Hipp wrote:
On 1/14/18, Christian Stærk wrote:
What do you think? Is this desirable?
I'm certainly willing to consider it, but I want to see some examples
before committed to this path.
As for pledge, it is a fairly simple interface. Online man page is here:
https
On 1/14/18, Christian Stærk wrote:
>
> What do you think? Is this desirable?
>
I'm certainly willing to consider it, but I want to see some examples
before committed to this path.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-dev mailing list
fossil-de
Hello fossil-dev,
I am working on a project where we want to use Fossil as the data
storage backend for a web application. The application is going to run
on OpenBSD and we want to take advantage of the security features in
OpenBSD as much as possible.
In this regard we want to reach out and
