arw authored 5 years ago and Thomas Preisner committed 3 years ago

When a hardware/software token has drifted too far into the future, autoresync
advances the counter to resync. This only happens if a sufficient number of
good tries happened in sequence. Each of those good tries will be denied, the
next one however will resync the counter.

make the linter STFU

See merge request !1

Got severely fucked up in commit
58d65e2e, so that is suddenly expects a
different config format, restore the old one.

test against the standard versions in stretch and buster as well as the
latest go release on each of them.

should be valid for long enough now hopefully

`make test` is currently failing when building with  sbuild because it tries to run the
postgres database as root, which is not allowed. Since the test cases are also run using the
Gitlab CI, we ignore this issue for now.

If len is zero the while loop is skipped and sent is never initialized.

All callers pass len > 0 so this issue doesn't occur in practice yet.

Scan() can return true despite encountering an error. Encountered while
writing a test for the read timeout, also included.

Fixes a -Wsign-conversion warning with clang.

Use -stretch images because libpam-wrapper is not in jessie.
Drop go1.7 because there is no go1.7-stretch image.

Runs tests with go versions 1.7 to 1.9 on our shared runner

Also add some cli tests, to be extended for existing subcommands.