keepassxc generate different TOTP code from Google Authenticator in 2.5.1 for secrete key require padding

[zydxt]

After updating to 2.5.1, keepassxc generate wrong TOTP code which is different from the code generated by Google Authenticator.

Expected Behavior

When I use keepassxc to set a RFC6283 TOTP password, and right click the record -> display TOTP QR code. Then I use google authenticator to scan the QR code keepassxc give me. The TOTP code generated by google auth and keepassxc should be same, and both them should be able to sign in my account (epic store for this case)

Current Behavior

When I use google auth to scan the QR code, I found that Google auth generate a different code. I can't use the code keepassxc generate to sign in my account (which is wrong) and I can use the code google auth generate to sign in.

Possible Solution

In the realease log, I found some fix for TOTP secrete key need padding. Maybe this change something aboute handle screte key.
#3764

Steps to Reproduce

1. Add a recode and set RFC6283 TOTP password. Use this key: IJHUOVSYLJHDOVCGKJKEKNZVLE3EGSBVJE2UGRBVIRHEUQKCJVKA (This is my legacy key, no use now)
   2.Input this key in Google Authenticator
2. Compare the code

Context

It generate wrong code and I can't sign in my account now.

Debug Info

KeePassXC - 2.5.1

Operating system: windows 10
CPU architecture: x86_64

Enabled extensions:

• EXTENSIONS

[droidmonkey]

Sync your time in your computer

[zydxt]

Sorry , My bad. I tested it on Linux, and It works. I found that my windows time is synced, but when I boot to Linux ( dual-boot ) It will mess up the windows time zone configuration, which make the totp code wrong