Commits
- Commit:
83a2644bfb1d8683faf024275a98600b0edc5063
- From:
- Omar Polo <op@omarpolo.com>
- Date:
convert remaining code to the imsg getters
Now gmid doesn't touch anymore the internals of the imsg structs.
- Commit:
6dec2ad700aac233ab001f91b8fa05813180eaba
- From:
- Omar Polo <op@omarpolo.com>
- Date:
convert most of gmid to the new imsg APIs
Makes parsing and handling of imsgs simpler / clearer. only crypto.c
is left as-is.
- Commit:
b03e976aa26d100ec1bf976dfdd005868395b490
- From:
- Omar Polo <op@omarpolo.com>
- Date:
convert to use imsg_get_fd()
since proc_forward_imsg() never forwards a file descriptor (it's
never called actually) just use -1 there.
- Commit:
3cb7e8d7ace5f0ba13193181d5f8d63aa1923e0b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ignore some errors from socket(2)
There's no much we can do if we resolv an IPv6 address but its
support is disabled in the current kernel, so ignore and go ahead.
Spotted while testing gmid i n a FreeBSD jail without IPv6.
- Commit:
8f8d721301fb5d8cf248fc89b0a74616fc1aa1ee
- From:
- Omar Polo <op@omarpolo.com>
- Date:
enable privsep crypto on all systems
now that we have a bundled libtls we can actually do this. Retain
the knob to disable it "just in case".
- Commit:
d72ac636bb2b5c5a6b9c946cc5fc69130ac62653
- From:
- Omar Polo <op@omarpolo.com>
- Date:
unbreak config_test() when !use_privsep_crypto
The new config_test() fails miserably when the privsep crypto engine is
not enabled. As a temporary workaround, forcibly disable it during
config_test() as we're not going to run anyway.
- Commit:
3b431c09d97f86f40f0f57a5d6d2e08681b1c65d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
try hard at loading the configuration during conftest (-n)
Attempt to do also a few more steps that were previously done only
at runtime. This can help verifying that the keypairs are matching
for example, but also that there are no typos in the path to the
root directories.
Was requested some time ago by Marian Mizik, thanks for the feature
request!
- Commit:
9abba172b6f9ff373dd1e45d7b9587d3bdd0afcf
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add `log syslog facility' to use a different syslog(3) facility
Was requested ages ago by Karl Jeacle, now that there is some better
support for configuring the logging there's no excuse to add this.
It helps with filtering from syslog.d / syslog.conf.
- Commit:
f23b708726fbc5c2a985fbdd50449891f4df87dd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
set the default logging style back to legacy
I think the condensed is better but it'll need to change post 2.0
to accomodate for logging the number of bytes read in the body of
a titan request (and it's weird to hardcode a zero there.) 2.0
will ship with the legacy logging style thus.
- Commit:
26df50981fe18b5f244293b203c1a1eb30759554
- From:
- Omar Polo <op@omarpolo.com>
- Date:
actually use the specified log style
- Commit:
46bcc4ea95b03fe81ad361ee02bd021a7618e5a9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add log syslog off; don't turn syslog off when log access is specified
- Commit:
226f13ece0b309abeee0ae8a4d8c9f049fe896a7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add ability to log to files with log access <path>
- Commit:
45c946b37bd2e22f095af6ac290fbf865eb595a1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
avoid use-after-free
- Commit:
a1ba9650a9f0cc0d9e70800d71769d32f927b939
- From:
- Omar Polo <op@omarpolo.com>
- Date:
revamp fastcgi configuration: make it per-location
this revamps the syntax in the configuration to better match httpd(8)
(and in general be less weird) and to allow per-location fastcgi
configurations.
the bare `param' is now deprecated, but for compatibility it acts
like `fastcgi param' would do now. Same story for `fastcgi <pathÂ>'.
- Commit:
71b02f6390ca350eee6c13259140143e34e0dd25
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename do_accept() -> server_accept()