Re: Pledge Policy for Tset Binary
Thanks Theo! I am working on it right now. On Wed, Mar 4, 2020 at 9:21 AM Theo de Raadt wrote: > shankarapailoor . wrote: > > > I was looking at the pledge policy for the tset binary and I was > wondering > > why wpath is necessary. I removed the group from the pledge and did some > > basic tests with the utility and there was no error. Removing any of the > > other groups produces an error so they seem necessary. Any assistance > would > > be appreciated. > > Yeah, I can't find a open-for-write. However this calls libcurses which > is a nest of vipers. > > Since you have already begun... > > As well as trying all options, please add tests which mix in all > potential environment variables which are used by the dependent > libraries. > > A bit more effort please, and if no cause can be found, then wpath > can be removed. > -- Regards, Shankara Pailoor
Re: Pledge Policy for Tset Binary
shankarapailoor . wrote: > I was looking at the pledge policy for the tset binary and I was wondering > why wpath is necessary. I removed the group from the pledge and did some > basic tests with the utility and there was no error. Removing any of the > other groups produces an error so they seem necessary. Any assistance would > be appreciated. Yeah, I can't find a open-for-write. However this calls libcurses which is a nest of vipers. Since you have already begun... As well as trying all options, please add tests which mix in all potential environment variables which are used by the dependent libraries. A bit more effort please, and if no cause can be found, then wpath can be removed.
Pledge Policy for Tset Binary
Hi, I was looking at the pledge policy for the tset binary and I was wondering why wpath is necessary. I removed the group from the pledge and did some basic tests with the utility and there was no error. Removing any of the other groups produces an error so they seem necessary. Any assistance would be appreciated. Regards, Shankara Pailoor
