Theo de Raadt writes:
> I have reviewed all the pledge using programs in the tree, and I do not
> see additional risk from this change.
>
> Who wants to take care of the commit?
I'll snag it!
>
> Josh Rickmar wrote:
>
>> The kern.somaxconn sysctl was previously permitted under the inet
>>
I have reviewed all the pledge using programs in the tree, and I do not
see additional risk from this change.
Who wants to take care of the commit?
Josh Rickmar wrote:
> The kern.somaxconn sysctl was previously permitted under the inet
> pledge, which allowed pledged Go applications to listen
On Mon, Feb 01, 2021 at 08:18:53PM +, Josh Rickmar wrote:
> The kern.somaxconn sysctl was previously permitted under the inet
> pledge, which allowed pledged Go applications to listen on AF_INET and
> AF_INET6 domains.
>
> https://marc.info/?l=openbsd-tech=158069595809463=2
>
The kern.somaxconn sysctl was previously permitted under the inet
pledge, which allowed pledged Go applications to listen on AF_INET and
AF_INET6 domains.
https://marc.info/?l=openbsd-tech=158069595809463=2
https://marc.info/?l=openbsd-cvs=158081099810301=2
But Go will also read this sysctl when
