Hello Aaron,
this looks like a Safeword Silver token.
To my knowledge the silver tokens are not HOTP/TOTP compatible.
The secret key (if it is not encrypted) looks like a 14 byte hex string,
which is 2 x 56bit, which - exactly like the "DES-Silver" indicated a
DES based proprietary algorithm.
Only the Safeword Alphine tokens followed the HOTP RFC4226 spec.
How many tokens are we talking here?
Kind regards
Cornelius
> --
> Please read the blog post about getting help
>
https://www.privacyidea.org/getting-help/.
>
> For professional services and consultancy regarding two factor
> authentication please visit
>
https://netknights.it/en/leistungen/one-time-services/
>
> In an enterprise environment you should get a SERVICE LEVEL AGREEMENT
> which suites your needs for SECURITY, AVAILABILITY and LIABILITY:
>
https://netknights.it/en/leistungen/service-level-agreements/
> ---
> You received this message because you are subscribed to the Google
> Groups "privacyidea" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
privacyidea...@googlegroups.com.
> To post to this group, send email to
priva...@googlegroups.com.
> Visit this group at
https://groups.google.com/group/privacyidea.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/privacyidea/aa26ee80-3bf1-45d1-94cf-eaece3c5e8cd%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
Cornelius Kölbel
corneliu...@netknights.it
+49 151 2960 1417
NetKnights GmbH
http://www.netknights.it
Landgraf-Karl-Str. 19, 34131 Kassel, Germany
Tel:
+49 561 3166797, Fax:
+49 561 3166798
Amtsgericht Kassel, HRB 16405
Geschäftsführer: Cornelius Kölbel