Nex
Flush
Where do you have this blurb from? In any case, the reference to IMEI in it is bullshit. FreeOTP only supports two 2FA algorithms, TOTP and HOTP. TOTP is a defined open standard just like HOTP is, and none of them use IMEI or any other device identifier anywhere. Like I said, there are other 2FA systems out there that indeed are tied to hardware identifiers, but this one is not. They usually come as closed source software, or on purpose-built hardware devices.
In theory you could use some unique device identifier as the shared OTP secret key, but in practice everyone just randomly generates these as it adds more security. Also, even if you wanted to go that way, it's the issuing party (the PCF forum software) which would need to know it at time of issuance, plus you can then still simply use the OTP secret, once issued, on any device to generate codes with.
Source: I am a software developer and actually have implemented TOTP 2FA authentication in some software I wrote.
In theory you could use some unique device identifier as the shared OTP secret key, but in practice everyone just randomly generates these as it adds more security. Also, even if you wanted to go that way, it's the issuing party (the PCF forum software) which would need to know it at time of issuance, plus you can then still simply use the OTP secret, once issued, on any device to generate codes with.
Source: I am a software developer and actually have implemented TOTP 2FA authentication in some software I wrote.