@
scott967
Thanks for your reply. I saw you already edited out Krypton from your post by now, so i don't need to mention much anymore about the two co-existing add-on generations (5.x/6.x).
Yep, i saw the switch to token-style auth - i already "de-obfuscated" the token to get the plain "old school style" api key from your token which i _could_ use for a fixed 5.x Krypton version of the add-on without further changes besides replacing the old key.
But i would not want to use your new key for a backport and make it accessible in plain before asking you since i don't know if you switched to the token method by intent to keep things at least a bit more obfuscated.
- Not knowing the reason why the old api key is suddenly invalid after so many years let me to believe that there might be a correlation to you switching to token style with the new key for the latest version
- Backporting the whole new token-style auth to version 5.6.0 (8+ years old) might be a bit too complicated because of the extensive differences in the code between then and now, i guess?
Core question maybe:
- Do you care if your new key would be used in a plain & non-obfuscated way for a quick-and-simple 5.x.x fixed version for Krypton?
No hurry at all and happy to wait for input whenever the time is right.
Good travels.