On Tue, Feb 10, 2015 at 04:34:40AM +, Rui Paulo wrote:
Author: rpaulo
Date: Tue Feb 10 04:34:39 2015
New Revision: 278494
URL: https://svnweb.freebsd.org/changeset/base/278494
Log:
Sanitise the coredump file names sent to devd.
While there, add a sysctl to turn this feature
On Feb 10, 2015, at 12:32 AM, Konstantin Belousov kostik...@gmail.com wrote:
And there is double-free somewhere.
Are you talking about the Jenkins error? I think that was the free(name) which
was the result of a mis-merge and which I fixed yesterday. Jenkins build #671
seems to be ok.
On Mon, 2015-02-09 at 20:46 -0800, Rui Paulo wrote:
On Feb 9, 2015, at 20:34, Rui Paulo rpa...@freebsd.org wrote:
Author: rpaulo
Date: Tue Feb 10 04:34:39 2015
New Revision: 278494
URL: https://svnweb.freebsd.org/changeset/base/278494
Log:
Sanitise the coredump file names sent
Author: rpaulo
Date: Tue Feb 10 04:34:39 2015
New Revision: 278494
URL: https://svnweb.freebsd.org/changeset/base/278494
Log:
Sanitise the coredump file names sent to devd.
While there, add a sysctl to turn this feature off as requested by
kib@.
Modified:
head/sys/kern/kern_sig.c
On Feb 9, 2015, at 20:34, Rui Paulo rpa...@freebsd.org wrote:
Author: rpaulo
Date: Tue Feb 10 04:34:39 2015
New Revision: 278494
URL: https://svnweb.freebsd.org/changeset/base/278494
Log:
Sanitise the coredump file names sent to devd.
While there, add a sysctl to turn this feature
On Feb 9, 2015, at 21:02, Ian Lepore i...@freebsd.org wrote:
Or... we could consider restoring devd to its original relatively benign
existance handling device-related events, and move handling of crash
dumps into a separate daemon which can shoulder the burden of security
for itself.
At
