extend the example

[authbind.git] / authbind.1

diff --git a/authbind.1 b/authbind.1
index 74d44d727d9ec00931c4bd6ec1dc601a5b5c5066..4376a53e4399a07cd51410e9cda6ab8133bc636c 100644 (file)
--- a/authbind.1
+++ b/authbind.1
@@ -139,6 +139,30 @@ will fail with
 .B ENOENT
 .RI ( "No such file or directory" ).
 .PP
+So for example an attempt by uid 432
+to bind to [2620:106:e002:f00f::21]:80
+would result in authbind calling
+.I access(2)
+on, in order,
+.RS
+.B /etc/authbind/byport/80
+.br
+.B /etc/authbind/byaddr/2620:106:e002:f00f::21,80
+.br
+.B /etc/authbind/byaddr/2620:106:e002:f00f:0:0:0:21,80
+.RE
+If none of these files exist, authbind will read
+.RS
+.B /etc/authbind/byuid/432
+.RE
+and search for a line to permit
+the relevant access; examples of lines which would do so are:
+.RS
+.B 2620:106:e002:f00f::21,80
+.br
+.B ::/0,80
+.RE
+.PP
 If a read error occurs, or the directory
 .B /etc/authbind
 cannot be accessed, then not only will