Virtual OTP token: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
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: | ||
{{Box-round|title=example uinf file for notepad, Save as "something".uinf|secu_uniotp<br> | |||
secu_uniotp<br> | STES1234567|0123456789012345678901234567890123456789|0000000000|0000000000|1|2014-01-21 10:06:35|6|050|060|}} | ||
STES1234567|0123456789012345678901234567890123456789|0000000000|0000000000|1|2014-01-21 10:06:35|6|050|060| | |||
For a more indepth description, the file format is:<br> | For a more indepth description, the file format is:<br> | ||
| Line 16: | Line 11: | ||
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 |(newline)<br> | 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 |(newline)<br> | ||
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)<br> | Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)<br> | ||
... | ...<br> | ||
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)<br> | Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)<br> | ||
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:26, 12 June 2018
Virtual token for testing
To create a uinf seed file for testing purposes, simply copy paste the following into notepad: Template:Box-round
For a more indepth description, the file format is:
secu_uniotp (newline)
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 |(newline)
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)
...
Serial name | secret key | counter 1 | counter 2 | token type | date last synchronized | digits | Authentication window | timestep | (newline)
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.
