2017-03-02 12:03 GMT-03:00 Sebastian Benoit <be...@openbsd.org>: > > EPERM on connect(2) can happen in netinet/tcp_output.c on a socket with > TF_SIGNATURE. As far as i can see its the only EPERM on tcp connect(). > > how far down the stack do we go when documenting errors? > > ok? > > diff --git lib/libc/sys/connect.2 lib/libc/sys/connect.2 > index 9c0cfb09d79..6f18e09cddf 100644 > --- lib/libc/sys/connect.2 > +++ lib/libc/sys/connect.2 > @@ -196,6 +196,9 @@ Either the socket is non-blocking or a previous call to > .Fn connect > was interrupted by a signal, and the connection attempt has not yet > been completed. > +.It Bq Er EPERM > +A TCP connection on a socket with socket option TCP_MD5SIG was > +attempted without configuring the security parameters correctly. > .El > .Pp > The following errors are specific to connecting names in the
OK renato@ -- Renato Westphal
