into /etc/machine-id *before* looking into /var/lib/dbus/machine-id and for
the few that don't patch them to look directly there.
Thanks sthen@ for the source ports seach.
reported by naddy@. If only cmake shipped a FindHUNSPELL.cmake module,
instead of having one installed by kdelibs (and thus, a hidden build
dep) and one in sonnet source tarball....
SECURITY: "hg serve --stdio could be tricked into granting authorized
users access to the Python debugger"
"dispatch: protect against malicious 'hg serve --stdio' invocations
(sec) Some shared-ssh installations assume that 'hg serve --stdio' is
a safe command to run for minimally trusted users. Unfortunately, the
messy implementation of argument parsing here meant that trying to
access a repo named '--debugger' would give the user a pdb prompt,
thereby sidestepping any hoped-for sandboxing. Serving repositories
over HTTP(S) is unaffected.
We're not currently hardening any subcommands other than 'serve'. If
your service exposes other commands to users with arbitrary repository
names, it is imperative that you defend against repository names of
'--debugger' and anything starting with '--config'.
The read-only mode of hg-ssh stopped working because it provided its
hook configuration to "hg serve --stdio" via --config parameter. This
is banned for security reasons now. This patch switches it to directly
call ui.setconfig(). If your custom hosting infrastructure relies on
passing --config to "hg serve --stdio", you'll need to find a
different way to get that configuration into Mercurial, either by
using ui.setconfig() as hg-ssh does in this patch, or by placing an
hgrc file someplace where Mercurial will read it. mitrandir@fb.com
provided some extra fixes for the dispatch code and for hg-ssh in
places that I overlooked."
for disaster. Can't work even with gcc, caught by clang.
Turns out this is just debugging shitz, not really necessary, just comment
it off (we could rewrite the whole thing to have separate scope or use
new/delete, but what's the point ? mozjs17 is going to die one day anyway)
FreeBSD doesn't see the issue 'cause they don't enable threads.
okay sthen@
