Skip to content

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

Description

@Palmik

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions