| Commit message (Collapse) | Author | Age |
| |
|
|
| |
well
|
| | |
|
| |
|
|
| |
This gets tlsdate and tlsdate-helper working on FreeBSD 9.2-RELEASE.
|
| |
|
|
|
|
|
|
|
|
|
| |
On FreeBSD 11-CURRENT this fixes the compilation failure:
src/util.c: In function 'file_write':
src/util.c:256: error: 'S_IRUSR' undeclared (first use in this function)
src/util.c:256: error: (Each undeclared identifier is reported only once
src/util.c:256: error: for each function it appears in.)
src/util.c:256: error: 'S_IWUSR' undeclared (first use in this function)
*** Error code 1
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
On FreeBSD 11-CURRENT this fixes the compilation failure:
In file included from ./src/proxy-bio.h:16,
from src/proxy-bio.c:38:
./src/util.h:46: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'wait_with_timeout'
./src/util.h:50: warning: 'struct timeval' declared inside parameter list
./src/util.h:50: warning: its scope is only this definition or declaration, which is probably not what you want
./src/util.h:51: warning: 'struct timeval' declared inside parameter list
./src/util.h:57: warning: 'struct timeval' declared inside parameter list
*** Error code 1
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This partially addresses Debian bug #704680
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Rudimentary support for HTTP Date headers
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Previously I had disabled it with #ifdef __linux__, but that's not
very good autoconf style.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Since I'm going on a personal crusade to kill off gmt_unix_time, I
should provide an alternative. That alternative can be the Date
header from HTTP -- unlike gmt_unix_time, the Date header is required
by the RFC to actually be an accurate clock-like clock, and nobody is
trying to get rid of it.
This code is pretty hack-ish and does some nonportable stuff, like
using memmem() and timegm(). It's not super-tolerant of
non-standards-compliant HTTP servers. I hope I didn't make any
pointer mistakes.
|
| |\
| |
| | |
tlsdate: add optional --showtime support for "raw"
|
| | |
| |
| |
| |
| | |
Update the man pages and simplify the processing of -V
and --showtime to share the optional argument path.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add support for optional arguments to --showtime, "raw" and "human".
Human readable output is what --showtime and -V do already. Passing
in --showtime=raw will tell tlsdate-helper to write the raw
unix time directly to stdout in host byte order.
The purpose of this change is to provide easier integration of
privilege isolation for time setting. If tlsdate is called from
a wrapper, like tlsdated, it should be possible to pass the time back
to a privileged time-setter with the minimum of needed parsing.
|
| |\ \
| |/
|/| |
Refactor event loop.
|
| |/
|
|
|
|
|
|
|
|
| |
Refactor the event loop to be modular and testable. Also, add support for
detecting corruption of the realtime clock, as can be caused by suspend/resume
cycles without an rtc battery. The event loop is now driven by a tree of events,
which are either sources (currently suspend/resume events, periodic events, and
network route events) or composite events.
Signed-off-by: Elly Fong-Jones <elly@leptoquark.net>
|
| |\
| |
| | |
Update CHANGELOG for integration tests.
|
| |/ |
|
| |\
| |
| | |
Add integration testing.
|
| |/
|
|
|
|
| |
These new integration tests mostly focus on tlsdated's subprocess code.
Signed-off-by: Elly Fong-Jones <elly@leptoquark.net>
|
| |\ |
|
| | |\
| | |
| | | |
Fix subprocess watching.
|
| | |/
| |
| |
| |
| |
| |
| | |
Currently, the subprocess watching code polls with a delay between attempts.
Instead, introduce wait_with_timeout() and use it, simplifying this code.
Signed-off-by: Elly Fong-Jones <elly@leptoquark.net>
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
tlsdated: remove rmrf()
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
This function, while handy and presently used safely, could become dangerous if
someone later adds a call to it that passes in attacker-controlled input.
Therefore, hardcode calls to unlink(2) and rmdir(2) for the files tlsdated
presently creates. This has the pleasant (?) side-effect of breaking unit-tests
whenever tlsdated creates files we don't explicitly list on disk.
BUG=None
TEST=unit
Signed-off-by: Elly Fong-Jones <ellyjones@chromium.org>
|
| | |
|