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

yuce / pot / 54 / 1
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: update-readme-mix-example
DEFAULT BRANCH: master
Ran 19 Feb 2020 04:28AM UTC
Files 2
Run time 0s
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

19 Feb 2020 04:27AM UTC coverage: 100.0%. Remained the same
54.1

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%)

1800.01 hits per line

Source Files on job 54.1
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 39
  • Travis Job 54.1
  • 21dbd074 on github
  • Prev Job for on hotp_return_interval (#52.2)
  • Next Job for on hotp_return_interval (#57.1)
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

© 2026 Coveralls, Inc