Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Marcus MERIGHI
ch...@nmedia.net (Chris Cappuccio), 2015.08.07 (Fri) 22:34 (CEST): > Maxime Villard [m...@m00nbsd.net] wrote: > > Now, I believe that this effort is too much for my spare time. If you > > want to say "thanks" to me for reporting this vulnerability, dear Sam, > > it's never too late. > > I put here

Re: small mv patch

2015-08-08 Thread Philip Guenther
On Fri, Aug 7, 2015 at 12:24 AM, Martijn van Duren wrote: > Hello tech@, > > I was reading mv.c and found two minor things in fastcopy: > 1) fd leak on seldom reached code I think this one is handled more cleanly by moving the "if (!blen)" block up before two open()s. That way if the malloc fail

Re: PF SMP: making anchor stack multithreaded

2015-08-08 Thread Alexandr Nedvedicky
Hello, I've reworked the anchor handling so the traversal uses true recursion now. Using recursion here will allow us to implement ruleset locking in nicer fashion. The idea is to split current pf_test_rule() into two functions: pf_test_rule() and pf_match_rule(). pf_step_into_anchor() is change

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Christian Schulte
Am 08/07/15 um 23:46 schrieb Alexey Suslikov: Christian Schulte schulte.it> writes: Now, I believe that this effort is too much for my spare time. Then why not release that scanner? That effort could be shared. What's so secret about it? You have been asked several times already. Start sha

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Ville Valkonen
Hello Maxime, On Aug 7, 2015 10:56 PM, "Maxime Villard" wrote: > > Well, I guess I'll have to admit that I find your attitude extremely > disrespectful. But I don't tend to feel particularly offended by this > kind of things, so it probably does not matter. > > > > Le 21/07/2015 12:31, sam a écri

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Alexey Suslikov
On Sat, Aug 8, 2015 at 2:21 PM, Christian Schulte wrote: > Am 08/07/15 um 23:46 schrieb Alexey Suslikov: >> >> Christian Schulte schulte.it> writes: >> Now, I believe that this effort is too much for my spare time. >>> >>> >>> Then why not release that scanner? That effort could be shared. W

[PATCH] relayd, fix crash on "Host: " HTTP 400 Bad Request and use-after-free

2015-08-08 Thread Hiltjo Posthuma
Hi! I was testing relayd and found an issue which would make relayd crash. Reproduce: Test config /etc/relayd.conf: http protocol "test" { pass response block url "host" return error } relay "testing" { listen on "127.0.0.1" port 8080

Re: Brainy: User-Triggerable Kernel Memory Leak in execve()

2015-08-08 Thread Christian Schulte
Am 08/08/15 um 15:06 schrieb Alexey Suslikov: On Sat, Aug 8, 2015 at 2:21 PM, Christian Schulte wrote: Am 08/07/15 um 23:46 schrieb Alexey Suslikov: Christian Schulte schulte.it> writes: Now, I believe that this effort is too much for my spare time. Then why not release that scanner? Th

Possible memory leak in sys/dev/ic/ti.c (was: Re: Brainy: User-Triggerable Kernel Memory Leak in execve())

2015-08-08 Thread Christian Schulte
While at it. I cannot test this as I do not have corresponding hardware. Index: sys/dev/ic/ti.c === RCS file: /cvs/src/sys/dev/ic/ti.c,v retrieving revision 1.12 diff -u -r1.12 ti.c --- sys/dev/ic/ti.c 22 Dec 2014 02:28:51 -

Re: autoinstall(8): using multiple set sources?

2015-08-08 Thread Philipp
Am 08.08.2015 01:26 schrieb Alexander Hall: Try adding Set name(s) = done Here, like you would manually do (albeit likely implicit by just pressing enter). Bit counterintuitive at first, but works! Thanks a bunch.