yitsushi / totp-cli

28%

master: 20%

LAST BUILD ON BRANCH v1.9.0

branch: v1.9.0

CHANGE BRANCH

x

Reset

• v1.9.0
• 125-vendor-package-for-gentoo
• 133-add-sha2
• 136-add-time-period
• 38-auto-versioning
• 47-clear-prefix
• 74-fix-update-error-handling
• 88-remaining-time
• 95-fix-no-newline-input
• add-prefix
• add-release-signing
• add-signing-keys-to-readme
• add-update-command
• dependabot/go_modules/filippo.io/age-1.2.1
• dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.3.0
• dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0
• dependabot/go_modules/golang.org/x/crypto-0.17.0
• dependabot/go_modules/golang.org/x/crypto-0.31.0
• document-default-cred-path
• fix-release-build
• import-command
• improve-kdf-test-pr-check
• main
• master
• pass-with-env
• put-windows-back
• refactor-storage
• refs/tags/v1.2.0
• refs/tags/v1.2.1
• refs/tags/v1.2.2
• refs/tags/v1.2.3
• refs/tags/v1.2.4
• refs/tags/v1.2.5
• refs/tags/v1.2.6
• refs/tags/v1.2.7
• refs/tags/v1.3.0
• refs/tags/v1.3.1
• refs/tags/v1.3.2
• refs/tags/v1.3.3
• refs/tags/v1.4.0
• refs/tags/v1.5.0
• refs/tags/v1.5.1
• refs/tags/v1.5.2
• refs/tags/v1.5.3
• refs/tags/v1.6.0
• refs/tags/v1.7.0
• remove-panic
• remove-update-command
• remove-util
• rename-account
• return-nil
• small-changes
• some-cleanup
• some-random-fixes
• try-to-fix-autocomplete
• update-checkout-action
• update-deps
• update-deps-20240619
• update-go-cleanup
• update-some-comments
• update-workflow-versions
• use-urfave
• v1.1.10
• v1.1.11
• v1.1.12
• v1.1.13
• v1.8.0
• v1.8.1
• v1.8.2
• v1.8.3
• v1.8.4
• v1.8.5
• v1.8.6
• v1.8.7
• v1.8.8
• v1.9.1
• v1.9.2

Build # 13551469725

Build Type

push

github

Committed by web-flow

Commit Message

feat: add sha256 and sha512 support (#135)

* feat: add sha256 and sha512 support

As the original implementation followed only RFC-4226, it had only SHA1
support. This covers a lot of tokens, but secure tokens are not SHA1, but
SHA2 based as described in RFC-6238.

Until now, I though only hardware tokens use SHA2 (SHA256, SHA512) and
maybe some edge cases, but not common. That was probably true almost 10
years ago when I originally created this tool. Today, even tho I didn't
see 256 or 512 tokens yet, I think it's more common, and soon they will
be used in a lot of places.

Resolves #133

References:
- https://github.com/yitsushi/totp-cli/issues/133
- https://www.ietf.org/rfc/rfc4226.txt
- https://www.ietf.org/rfc/rfc6238.txt

Signed-off-by: Victoria Nadasdi <victoria@efertone.me>

Run Details

2 of 124 new or added lines in 13 files covered. (1.61%)

3 existing lines in 1 file now uncovered.

300 of 1056 relevant lines covered (28.41%)

2.61 hits per line