On Wed, 4 Apr 2018 09:27:10 -0700
Kees Cook wrote:
> On Wed, Apr 4, 2018 at 12:49 AM, Peter Zijlstra wrote:
> > On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote:
> >> If you are concerned about attack surface, I could make it a bit more
> >> difficult to tweak by malicious softwa
On Wed, Apr 4, 2018 at 12:49 AM, Peter Zijlstra wrote:
> On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote:
>> If you are concerned about attack surface, I could make it a bit more
>> difficult to tweak by malicious software. What about the patch below?
>> It would be much more diffic
On Wed, 4 Apr 2018 09:49:27 +0200
Peter Zijlstra wrote:
> On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote:
> > If you are concerned about attack surface, I could make it a bit more
> > difficult to tweak by malicious software. What about the patch below?
> > It would be much more d
On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote:
> If you are concerned about attack surface, I could make it a bit more
> difficult to tweak by malicious software. What about the patch below?
> It would be much more difficult to modify this knob from an attack
> vector.
Not if you
On Wed, 4 Apr 2018 07:43:49 +1000
"Tobin C. Harding" wrote:
> > static noinline_for_stack
> > char *restricted_pointer(char *buf, char *end, const void *ptr,
> > @@ -1962,6 +1963,10 @@ char *pointer(const char *fmt, char *buf, char *end,
> > void *ptr,
> > return pointer_string(buf
On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote:
> On Tue, 3 Apr 2018 13:07:58 -0700
> Kees Cook wrote:
>
> > On Tue, Apr 3, 2018 at 12:41 PM, Steven Rostedt wrote:
> > > Both trace_debug is set and kptr_restrict is set to zero in the same
> > > code that produces the above banner
On Tue, 3 Apr 2018 13:07:58 -0700
Kees Cook wrote:
> On Tue, Apr 3, 2018 at 12:41 PM, Steven Rostedt wrote:
> > Both trace_debug is set and kptr_restrict is set to zero in the same
> > code that produces the above banner. This will allow trace_printk() to
> > not be affected by security code, as
On Tue, Apr 3, 2018 at 12:41 PM, Steven Rostedt wrote:
> Both trace_debug is set and kptr_restrict is set to zero in the same
> code that produces the above banner. This will allow trace_printk() to
> not be affected by security code, as trace_printk() should never be run
> on a machine that needs
8 matches
Mail list logo