On Mon, Jul 23, 2018 at 11:02:04PM +0200, Kamil Rytarowski wrote:
> We need to maintain a function to translate certain ranges to
> shadow/meta/origin/etc. We cannot map arbitrarily wide ranges to them.
Can we extend the pax note (or create a new one) and make the sanitizers
link that in? Then
On 23.07.2018 21:32, Joerg Sonnenberger wrote:
> On Mon, Jul 23, 2018 at 07:13:49PM +0200, Kamil Rytarowski wrote:
>> We need to have stack, heap and code of a program in predictable (and
>> quite narrow) ranges and thus ASLR disabled or less aggressive.
>
> What for? Nothing in the sanitizer
On Mon, Jul 23, 2018 at 07:13:49PM +0200, Kamil Rytarowski wrote:
> We need to have stack, heap and code of a program in predictable (and
> quite narrow) ranges and thus ASLR disabled or less aggressive.
What for? Nothing in the sanitizer design should require that. The only
requirement should be
Hello,
There are a couple of ways of using a yubikey as a certificate source
for use with SSH. One is as a CCID device via PC/SC Lite and the other
is via GPG.
Going down the former approach, using PC/SC Lite to get setup from
scratch (ignoring keygen), install pcsc-lite (as the middleware) and
On 23.07.2018 15:09, Joerg Sonnenberger wrote:
> On Mon, Jul 23, 2018 at 06:24:09PM +0530, Siddharth Muralee wrote:
>>>
>>>
>>> (1) An implementation detail of userland shouldn't be leaked into the
>>> kernel boot (!) process.
>>>
>>
>> Okay. I think this makes sense(I am still pretty new to
On Mon, Jul 23, 2018 at 06:24:09PM +0530, Siddharth Muralee wrote:
> >
> >
> > (1) An implementation detail of userland shouldn't be leaked into the
> > kernel boot (!) process.
> >
>
> Okay. I think this makes sense(I am still pretty new to NetBSD) - Can you
> suggest some other location/config
>> I have recently been working on adding a new boot flag for disabling
>> ASLR during boot. [...useful for some userland stuff...]
What's wrong with just configuring a kernel without any ASLR at all for
such work?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against
On 23.07.2018 14:54, Siddharth Muralee wrote:
>
> (1) An implementation detail of userland shouldn't be leaked into the
> kernel boot (!) process.
>
>
> Okay. I think this makes sense(I am still pretty new to NetBSD) - Can
> you suggest some other location/config that can be used.
>
Date:Mon, 23 Jul 2018 14:48:06 +0200
From:Martin Husemann
Message-ID: <20180723124806.gf18...@mail.duskware.de>
| Why don't you just use /etc/sysctl.conf?
I think that would be a little late, by the time anything in userland
gets a chance to do anything at all
>
>
> (1) An implementation detail of userland shouldn't be leaked into the
> kernel boot (!) process.
>
Okay. I think this makes sense(I am still pretty new to NetBSD) - Can you
suggest some other location/config that can be used.
> (2) There is no fundamental issue that makes the sanitizers
On 23.07.2018 14:48, Martin Husemann wrote:
> On Mon, Jul 23, 2018 at 06:11:49PM +0530, Siddharth Muralee wrote:
>> Hello,
>>I have recently been working on adding a new boot flag for disabling
>> ASLR during boot. I feel that this is useful since MKSANITZER userland
>> (specifically Address
On Mon, Jul 23, 2018 at 06:11:49PM +0530, Siddharth Muralee wrote:
> Hello,
>I have recently been working on adding a new boot flag for disabling
> ASLR during boot. I feel that this is useful since MKSANITZER userland
> (specifically Address Sanitizer, Thread Sanitizer, and Memory Sanitizer)
Hello,
I have recently been working on adding a new boot flag for disabling
ASLR during boot. I feel that this is useful since MKSANITZER userland
(specifically Address Sanitizer, Thread Sanitizer, and Memory Sanitizer)
requires ASLR to be disabled. Till now it was hardcoded in the kernel to be
13 matches
Mail list logo
