Bitwarden QR code instructions in readme

[dragonfly8677]

Description

Hey there.

I used the steamguard qr code to generate a QR code and added it to bitwarden. Initially it printed the wrong code (just numbers, e.g. 12345) but after some googling I managed to figure out how to fix it.

The QR code generates a link like the following: optauth://totp/Steam:username?secret=ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789&issuer=Steam. However, by changing this url to just steam://ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789, it now prints correct codes with letters, e.g. ABC12.

I figured that something about that could perhaps be added to the readme? Maybe it could even help for Google Authenticator or Authy to use those urls, as those are mentioned as incombatible, or maybe it's just a bitwarden specific thing I'm not sure.

[dyc3]

It's probably a bitwarden specific feature. If anything, I would say this is a bitwarden issue. The QR code url is provided verbatim from what steamguard-cli gets from the steam API, so bitwarden is interpreting the URL incorrectly.

Though, I wouldn't be opposed to a --bitwarden flag or something. I'd accept a PR for that.

[gwuen]

Related: Both KeePassXC and PyOTP (used by GNOME Secrets) additionally require encoder=steam, and specifically KeePassXC will display one additional character if digits=5 is not specified.

Though I think this should be widely compatible and does not need to be hidden behind a flag, some testing with other authenticators would be good. Example:

otpauth://totp/Steam:username?secret=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&period=30&digits=5&issuer=Steam&encoder=steam