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
I have been using Perplexica for some time now and am generally very satisfied. I have stored my API keys in config.toml. So that my installation is not publicly accessible, I have provided the domain with .htaccess directory protection. Unfortunately, access was still temporarily possible due to unfavorable circumstances. As the API keys can be viewed unencrypted via the settings, they were annoyingly stolen and used without permission, which resulted in unnecessarily high costs for me.
I am aware that the temporary accessibility of my Perplexica installation was my own fault. Nevertheless, in my opinion it would make sense to no longer display the API keys stored within config.toml in the Perplexica settings in unencrypted form so that they cannot be read/copied so easily.
The text was updated successfully, but these errors were encountered:
I have been using Perplexica for some time now and am generally very satisfied. I have stored my API keys in config.toml. So that my installation is not publicly accessible, I have provided the domain with .htaccess directory protection. Unfortunately, access was still temporarily possible due to unfavorable circumstances. As the API keys can be viewed unencrypted via the settings, they were annoyingly stolen and used without permission, which resulted in unnecessarily high costs for me.
I am aware that the temporary accessibility of my Perplexica installation was my own fault. Nevertheless, in my opinion it would make sense to no longer display the API keys stored within config.toml in the Perplexica settings in unencrypted form so that they cannot be read/copied so easily.
The text was updated successfully, but these errors were encountered: