Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to API over HTTPs --> API key transmitted without encryption in the request body #64

Open
Palmik opened this issue Oct 16, 2023 · 0 comments

Comments

@Palmik
Copy link

Palmik commented Oct 16, 2023

Hey, it looks like your SSL certificate is not valid, as I can't access your API endpoints over HTTPs. This meas that the API-key is transmitted in the clear, and any serer between the client and you API (or e.g. anyone on the same LAN) can read the API key.

curl: (60) SSL: no alternative certificate subject name matches target host name 'analytics.eventregistry.org'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant