Virtual OTP token: Difference between revisions
From SecuTech Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
To create a uinf seed file for testing purposes, simply copy paste the following into notepad: | To create a uinf seed file for testing purposes, simply copy paste the following into notepad: | ||
<source lang="uinf">secu_uniotp | <source lang="uinf">secu_uniotp | ||
STES1234567|0123456789012345678901234567890123456789|0000000000|0000000000|1|2014-01-21 10:06:35|6|050|060|</source> | |||
For a more indepth description, the file format is:<br> | For a more indepth description, the file format is:<br> | ||
<source lang="uinf"> | |||
Serial name | secret key (40 hex characters or 20 ascii) | counter 1 | counter 2 | token type (1 = HOTP, 2 = TOTP, 3 = OCRA) | date last synchronized | digits | Authentication window | timestep | | secu_uniotp | ||
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | | Serial name | secret key (40 hex characters or 20 ascii) | counter 1 | counter 2 | token type (1 = HOTP, 2 = TOTP, 3 = OCRA) | date last synchronized | digits | Authentication window | timestep | | ||
... | Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | | ||
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | | ... | ||
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | | |||
</source> | |||
For testing purposes, many virtual tokens can be created this way. Note that once a secret key format is used, it must stay in that format for the rest of the secret keys. ASCII filetype may add additional symbols when saved, it is recommended to use hex unless a "smart" editor is used. For example, [https://notepad-plus-plus.org Notepad++] with [https://sourceforge.net/projects/npp-plugins/files/Hex%20Editor/ hex editor] can be used to check if the secret key has more characters then 20. | For testing purposes, many virtual tokens can be created this way. Note that once a secret key format is used, it must stay in that format for the rest of the secret keys. ASCII filetype may add additional symbols when saved, it is recommended to use hex unless a "smart" editor is used. For example, [https://notepad-plus-plus.org Notepad++] with [https://sourceforge.net/projects/npp-plugins/files/Hex%20Editor/ hex editor] can be used to check if the secret key has more characters then 20. | ||
Revision as of 17:40, 12 June 2018
Virtual token for testing
To create a uinf seed file for testing purposes, simply copy paste the following into notepad:
secu_uniotp
STES1234567|0123456789012345678901234567890123456789|0000000000|0000000000|1|2014-01-21 10:06:35|6|050|060|For a more indepth description, the file format is:
secu_uniotp
Serial name | secret key (40 hex characters or 20 ascii) | counter 1 | counter 2 | token type (1 = HOTP, 2 = TOTP, 3 = OCRA) | date last synchronized | digits | Authentication window | timestep |
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep |
...
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep |For testing purposes, many virtual tokens can be created this way. Note that once a secret key format is used, it must stay in that format for the rest of the secret keys. ASCII filetype may add additional symbols when saved, it is recommended to use hex unless a "smart" editor is used. For example, Notepad++ with hex editor can be used to check if the secret key has more characters then 20.
