| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Relevant OpenBSD changelog:
> o AF_UNIX socket bind(2) and connect(2) now follow unveil(2)
> configuration.
|
| | |
|
| |
|
|
|
| |
capsicum is too impractical and removing it will allow much more
straightforward code.
|
| |
|
|
|
| |
My thinking here is that it's better to not allocate in response to
incoming connections. This also just makes the code a little simpler.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
LibreSSL is "a modified version of that library".
|
| | |
|
| |
|
|
| |
So that calico doesn't need any libs even on Linux.
|
| |
|
|
|
|
|
| |
This fixes a major issue that somehow didn't surface until upgrading to
FreeBSD 12.1-RELEASE-p6, where since calico doesn't grant the
CAP_SETSOCKOPT capability on accepted sockets, pounce crashes trying to
set keepalive on sockets on receives from it.
|
| |
|
|
| |
https://www.gnu.org/licenses/gpl-faq.en.html#GPLIncompatibleLibs
|
| |
|
|
| |
We need to ignore SIGPIPE anyway for other platforms.
|
| |
|
|
|
|
| |
There seems to be no guidance on how an application should set this
parameter. However, every system I've looked at will limit the value to
some default maximum, usually 128.
|
| | |
|
| | |
|
| |
|
|
| |
These are really just regular arrays masquerading as VLAs.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
My understanding is that sun_path need not be nul-terminated, but I
didn't notice that SUN_LEN actually requires it.
> The length of UNIX-domain address, required by bind(2) and connect(2),
> can be calculated by the macro SUN_LEN() defined in <sys/un.h>. The
> sun_path field must be terminated by a NUL character to be used with
> SUN_LEN(), but the terminating NUL is not part of the address.
Thanks to Duncan Overbruck <mail@duncano.de> for the report.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Notwithstanding any other provision of this License, if you modify the
> Program, your modified version must prominently offer all users
> interacting with it remotely through a computer network (if your version
> supports such interaction) an opportunity to receive the Corresponding
> Source of your version by providing access to the Corresponding Source
> from a network server at no charge, through some standard or customary
> means of facilitating copying of software.
This potentially means that every freenode user, for example, is
interacting with this software, and offering the corresponding source to
each of them is an unreasonable burden.
|
| | |
|
| | |
|
| | |
|
|
|
pounce can't accept connections from it yet though!
|
