Login

Recent searches

No recent searches

Search options

Not available on mastodon.zunda.ninja.
mastodon.zunda.ninja is one of the many independent Mastodon servers you can use to participate in the fediverse.
Zundon is a single user instance as home of @zundan as well as a test bed for changes of the code.

Administered by:

Server stats:

1
active users

mastodon.zunda.ninja: AboutPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.4+36feaf88-ruby-3.4.2

Public
zunda

RFC 6238にはTOTPの桁数は規定されていないし参考の実装は8桁を生成しているように見える🤔

TOTP: Time-Based One-Time Password Algorithm
https://datatracker.ietf.org/doc/html/rfc6238

IETF DatatrackerRFC 6238: TOTP: Time-Based One-Time Password AlgorithmThis document describes an extension of the One-Time Password (OTP) algorithm, namely the HMAC-based One-Time Password (HOTP) algorithm, as defined in RFC 4226, to support the time-based moving factor. The HOTP algorithm specifies an event-based OTP algorithm, where the moving factor is an event counter. The present work bases the moving factor on a time value. A time-based variant of the OTP algorithm provides short-lived OTP values, which are desirable for enhanced security. The proposed algorithm can be used across a wide range of network applications, from remote Virtual Private Network (VPN) access and Wi-Fi network logon to transaction-oriented Web applications. The authors believe that a common and shared algorithm will facilitate adoption of two-factor authentication on the Internet by enabling interoperability across commercial and open-source implementations. This document is not an Internet Standards Track specification; it is published for informational purposes.
Public
zunda

RFC 4226ではHOTPを6桁以上と規定して数字のみが望ましいとしてる
https://datatracker.ietf.org/doc/html/rfc4226#section-4

IETF DatatrackerRFC 4226: HOTP: An HMAC-Based One-Time Password AlgorithmThis document describes an algorithm to generate one-time password values, based on Hashed Message Authentication Code (HMAC). A security analysis of the algorithm is presented, and important parameters related to the secure deployment of the algorithm are discussed. The proposed algorithm can be used across a wide range of network applications ranging from remote Virtual Private Network (VPN) access, Wi-Fi network logon to transaction-oriented Web applications. This work is a joint effort by the OATH (Open AuTHentication) membership to specify an algorithm that can be freely distributed to the technical community. The authors believe that a common and shared algorithm will facilitate adoption of two-factor authentication on the Internet by enabling interoperability across commercial and open-source implementations. This memo provides information for the Internet community.
Public
zunda

この例からいろいろQRコードを作ってIIJ SmartKeyに登録してみました。世の中のTOTPはだいたい6桁か8桁ぽい。
https://github.com/google/google-authenticator/wiki/Key-Uri-Format#examples

左から、桁数指定なし(6桁になった)
$ echo -n 'otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example' | qrencode -o qr.png

digits=8を指定(8桁になった。こんな狭いの初めてみた!!)
$ echo -n 'otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&digits=8' | qrencode -o qr.png

digits=10を指定(QR code scan errorと表示して登録しない)
$ echo -n 'otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&digits=10' | qrencode -o qr.png

この他、digits=6だと6桁として登録でき、digits=7も登録しないようです。

otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example
otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&digits=8
otpauth://totp/Example:alice@google.com?secret=JBSWY3DPEHPK3PXP&issuer=Example&digits=10
ExploreLive feeds
About