socket_wrapper.git/doc, branch master

swrap: export a public socket_wrapper_indicate_no_inet_fd() helper function

2021-03-15T07:04:58+00:00

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14640

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andreas Schneider

swrap: introduce a socket_wrapper_noop.so and socket_wrapper.h to provide noop stubs

2021-03-15T07:04:58+00:00

Applications with the need to call socket_wrapper_enabled() should link
against -lsocket_wrapper_noop in order to resolve the symbol at
link time.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14640

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andreas Schneider

doc: Add website to manpage

2021-02-02T09:30:04+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Stefan Metzmacher

doc: Define doctype for manpage

2021-02-02T09:28:59+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Stefan Metzmacher

doc: Rename socket_wrapper.1.txt to socket_wrapper.1.adoc

2021-02-02T09:26:07+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Stefan Metzmacher

swrap: add basic support for fd-passing via SCM_RIGHTS

2021-02-02T09:23:33+00:00

We only allow passing up to 6 fds in a single sendmsg call,
in order to keep the logic simple.

That's more than enough for Samba's use of fd-passing,
there we only pass a single fd and the fd will be
closed in the sender on success. It means it's ok
to keep the socket_info.io.pck_{snd,rcv} fields per process
and the PCAP generation will still work as expected.

If these constraints turn out to be a problem for other applications,
we need to change to a more complex design and move the socket_info array
into a shared memory file and use shared robust mutexes.

But for now we just want to support multi-channel testing in Samba.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=11899

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Anoop C S 
Reviewed-by: Andreas Schneider

doc: Document SOCKET_WRAPPER_DIR_ALLOW_ORIG

2020-06-22T14:44:30+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Andreas Schneider 
Reviewed-by: Stefan Metzmacher

swrap: add support for SOCKET_WRAPPER_IPV4_NETWORK=10.53.57.0

2020-03-21T12:59:42+00:00

With this 10.53.57.XX/8 addresses are used instead of
127.0.0.XX/8. Note the broadcast address is 127.255.255.255
or 10.255.255.255 (and not 10.53.57.255!).

Some applications, e.g. Samba have some special behavior for
loopback addresses.

This allows more realistic tests and triggers the more common
code paths.

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andreas Schneider

doc/socket_wrapper.1: clarify the possible values for SOCKET_WRAPPER_DEFAULT_IFACE

2020-03-21T12:59:42+00:00

The valid range for  starts with 1 (the default) and ends with 64.

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andreas Schneider

doc: Fix some typos in the manpage

2019-03-21T07:42:41+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Ralph Boehme