• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

yuce / pot / 54
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: update-readme-mix-example
DEFAULT BRANCH: master
Ran 19 Feb 2020 04:28AM UTC
Jobs 4
Files 2
Run time 9s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
54

push

travis-ci

nalundgaard
Add return_interval option to valid_hotp

There is a flaw in the `valid_hotp` logic introduced in https://github.com/yuce/pot/pull/15 that prevents it from being effectively used: because it returns a raw `boolean`, there is no way to know *which* interval matched: the next one, the 1000th one, or somewhere in between? In order to effectively implement a proper HOTP scheme, you need to track the interval number of the last valid HOTP to prevent its reuse, OR the reuse of a HOTP from any previous interval.

For backwards compatibility, I have retained the default `boolean()` response, but if the `return_interval` option is set, the interval will be returned when a hotp is valid, like `{true, interval()}`.

140 of 140 relevant lines covered (100.0%)

7200.06 hits per line

Jobs
ID Job ID Ran Files Coverage
1 54.1 19 Feb 2020 04:28AM UTC 0
100.0
Travis Job 54.1
2 54.2 19 Feb 2020 04:28AM UTC 0
100.0
Travis Job 54.2
3 54.3 19 Feb 2020 04:28AM UTC 0
100.0
Travis Job 54.3
4 54.4 19 Feb 2020 04:28AM UTC 0
100.0
Travis Job 54.4
Source Files on build 54
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Travis Build #54
  • 21dbd074 on github
  • Prev Build on hotp_return_interval (#52)
  • Next Build on hotp_return_interval (#57)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc