You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TOTPGenerator used for webscans needs a seed that is provided as an hex, base32 or base64 encoded string most of the time.
Currently there can be issues based on the chosen charset, if the seed is decoded and saved as string or is encoded afterwards again. Information can be lost or changed during this process.
Solution
Use the encoded string and decode it only when it is required. Do not transform the datatypes if not necessary.
The text was updated successfully, but these errors were encountered:
winzj
changed the title
Use the encoded TOTP seed inside the TOTPGenerator instead of type conversions
Fix TOTP generation by using the encoded TOTP seed inside the TOTPGenerator instead of previous type conversions
Jan 13, 2025
winzj
changed the title
Fix TOTP generation by using the encoded TOTP seed inside the TOTPGenerator instead of previous type conversions
Fix TOTP seed handling inside ZAP wrapper
Jan 13, 2025
Situation
The TOTPGenerator used for webscans needs a seed that is provided as an hex, base32 or base64 encoded string most of the time.
Currently there can be issues based on the chosen charset, if the seed is decoded and saved as string or is encoded afterwards again. Information can be lost or changed during this process.
Solution
Use the encoded string and decode it only when it is required. Do not transform the datatypes if not necessary.
The text was updated successfully, but these errors were encountered: