On 7/13/18, Warren Young wrote:
>
> chroot() might even be strong enough given the tight scoping.
Just checking to make sure you know: If you launch Fossil as root, it
will automatically put itself into a chroot jail in the directory
containing the repository, then change its userid and groupid
As a defense against DoS attacks, Fossil has a feature were it refuses
to run certain expense web pages (ex: creating new tarballs) if the
system load averages is too high. Fossil uses the getloadavg()
interface to compute this. On Linux, getloadavg() requires that /proc
be mounted. So, if you
On Jul 13, 2018, at 7:09 PM, Richard Hipp wrote:
>
> So, if you want to use the rate limiting feature on
> Linux, you will need /proc mounted in your chroot jail. I wish there
> were a better way…
That’s actually one of the older features of cgroups. Maybe take a look?
> openBSD -current x64
> $ cc -v
> OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
> Target: amd64-unknown-openbsd6.3
> Thread model: posix
> InstalledDir: /usr/bin
>
Ok, I think I found the problem. This info was very helpful.
Indeed, the *BSD platforms have all the
On Fri 13 Jul 2018 5:08 AM, Artur Shepilko wrote:
> > openBSD -current x64
> > $ cc -v
> > OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
> > Target: amd64-unknown-openbsd6.3
> > Thread model: posix
> > InstalledDir: /usr/bin
> >
>
> Ok, I think I found the problem.
On 07/11/18 16:10, Warren Young wrote:
On Jul 10, 2018, at 8:58 PM, Andy Goth wrote:
I thought it interesting that he spoke of merging as if it were a
distinct task in the workflow for adding a file.
Did he check the file in on a branch and then merge it down to trunk?
No he did not, but
On 07/13/18 12:23, Warren Young wrote:
In my public Fossil projects, the policy is that any checkin that is
potentially destabilizing should be done on a branch, as should any
coherent line of work that will require multiple checkins to complete.
Trunk is ideally stable at all times, so as long
Whom should I be talking to regarding Chiselapp questions? I want to
know if there's a reason why it uses Fossil version 2.1 [83e3445f67] and
if there are any plans to upgrade.
I've not gotten any email replies from Roy Keene in a long time, neither
regarding Tcl nor Chiselapp, though I know
On Jul 13, 2018, at 9:39 AM, Andy Goth wrote:
>
> On 07/11/18 16:10, Warren Young wrote:
>> On Jul 10, 2018, at 8:58 PM, Andy Goth wrote:
>>> I thought it interesting that he spoke of merging as if it were a
>>> distinct task in the workflow for adding a file.
>> Did he check the file in on a
On Fri 13 Jul 2018 4:22 PM, David Mason wrote:
> So I guess this is what Warren had in mind. Posting this in case it helps
> somebody on the list.
>
Taking this offtopic a little bit more...let's talk about VPNs.
Don't use PPTP and don't get tangled up in ipsec configuration hell.
Be happy
On Jul 13, 2018, at 3:13 PM, Warren Young wrote:
>
> Now paste in an equivalent number of ‘a’ characters, and you get 0 bits of
> entropy. Strictly speaking, you get 1 bit of entropy for the whole message,
> but it shows 0 because the calculator is rounding the result off to 3
> significant
It's still me -- though I don't check email that often, and when I do I
don't read all of it, normally just the subject and sometimes the From.
Upgrading from Fossil 2.1 to something more recent hasn't been a
priority; I have to go through the versions and verify no new features
will cause
On Jul 13, 2018, at 3:13 PM, Warren Young wrote:
>
> 2. Add a dollar sign to the message, and bpc goes up a bit. (This conflicts
> with your report that adding a special character didn’t change it, but it did
> for me.)
I just realized where the discrepancy comes from: you *replaced* one
On Jul 13, 2018, at 2:13 PM, Roy Keene wrote:
>
> Upgrading from Fossil 2.1 to something more recent hasn't been a priority; I
> have to go through the versions and verify no new features will cause
> problems when hosting untrusted repositories, and I haven't done that.
I guess you’re
I use a password generator of my own design - basically takes the userid,
concatenated with a fairly long secret phrase, and then I do SHA1 and
convert it to base64, giving a password like:
Acgq75VpCWjdsJaa5abe9JeX3I (don't worry, this isn't a real password to
anything)
After Warren's comment
On Jul 13, 2018, at 2:22 PM, David Mason wrote:
>
> Acgq75VpCWjdsJaa5abe9JeX3I (don't worry, this isn't a real password to
> anything)
>
> …I fed this through an online entropy calculator and got 4.29 bits of Shannon
> entropy
That calculator is giving you bits *per character*.
You can
16 matches
Mail list logo
