g...@oat.com wrote:
> Theo de Raadt wrote:
> After pledge, 80% of the base programs were converted to pledge-assisted
> priv-drop, because it was really obvious that "initialization code"
> could
> and should be moved earlier in the program, so that pledge (or multiple
> p
Theo de Raadt wrote:
After pledge, 80% of the base programs were converted to pledge-assisted
priv-drop, because it was really obvious that "initialization code"
could
and should be moved earlier in the program, so that pledge (or multiple
pledge calls dropping pe
William Ahern wrote:
> Rather, the point of pledge and unveil is to make that
> deliberate refactoring as pleasant and minimal as is practicable.
Indeed, after the first 10 programs were converted to use pledge, it
became very obvious what would happen next:
"priv-drop everything"
The firs
On 2 Jun 2023, at 20:35, William Ahern wrote:
On Fri, Jun 02, 2023 at 04:24:31PM +0100, Leah Rowe wrote:
Hi everyone,
I had an interesting idea for OpenBSD. Haven't tried it yet. I'm
wondering what other people think of it? The idea is, thus:
1) Do execution tracing and just run a program.
On Fri, Jun 02, 2023 at 04:24:31PM +0100, Leah Rowe wrote:
>
> Hi everyone,
>
> I had an interesting idea for OpenBSD. Haven't tried it yet. I'm
> wondering what other people think of it? The idea is, thus:
>
> 1) Do execution tracing and just run a program. Do everything possible
> in it to the
Theo de Raadt wrote in
<93466.1685743...@cvs.openbsd.org>:
|We will wait for the demo.
...
|Leah Rowe wrote:
...
|> Yeah I was kinda thinking, just have it be a tool to *assist* but not
|> to automatically pledge the program itself. It wouldn't replace
|> human-performed auditing or analys
We will wait for the demo.
Leah Rowe wrote:
> Hi Theo,
>
> On Fri, 02 Jun 2023 11:03:40 -0600
> "Theo de Raadt" wrote:
>
> > Additionally the two outcomes of this will be:
> >
> > 1. Don't call pledge in the program.
> >
> > 2. Use pledge("audio bpf chown cpath disklabel dns dpath drm erro
Hi Theo,
On Fri, 02 Jun 2023 11:03:40 -0600
"Theo de Raadt" wrote:
> Additionally the two outcomes of this will be:
>
> 1. Don't call pledge in the program.
>
> 2. Use pledge("audio bpf chown cpath disklabel dns dpath drm error
> exec fattr flock getpw id inet mcast pf proc prot_exec ps recv
Leah Rowe wrote:
> Hi everyone,
>
> I had an interesting idea for OpenBSD. Haven't tried it yet. I'm
> wondering what other people think of it? The idea is, thus:
>
> 1) Do execution tracing and just run a program. Do everything possible
> in it to the fullest extent feasible and get an entire
How do you ensure you have coverage of all the operational choices
the program makes?
How about we what you propose and remove all the bugs and then we
don't need pledge?
Anyone who has done a 3nd year computer science course knows why this
does not work.
Leah Rowe wrote:
>
>
> Hi everyone,
On Fri, Jun 02, 2023 at 04:24:31PM +0100, Leah Rowe wrote:
>
> Hi everyone,
>
> I had an interesting idea for OpenBSD. Haven't tried it yet. I'm
> wondering what other people think of it? The idea is, thus:
>
> 1) Do execution tracing and just run a program. Do everything possible
> in it to the
11 matches
Mail list logo
