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

why is this called *ssl* ip #31

Closed
kumavis opened this issue Sep 14, 2023 · 3 comments
Closed

why is this called *ssl* ip #31

kumavis opened this issue Sep 14, 2023 · 3 comments

Comments

@kumavis
Copy link

kumavis commented Sep 14, 2023

unclear what the role of "ssl" is in the name as the service doesnt seem to do anything ssl specific

@cunnie
Copy link
Owner

cunnie commented Sep 16, 2023

Hi @kumavis

unclear what the role of "ssl" is in the name as the service doesnt seem to do anything ssl specific

You're right—it doesn't do anything SSL-specific, but it did in its first incarnation (2015?): we had a wildcard certificate and private key that we released to the public for *.sslip.io so that developers could use a valid certificate for, say, 127-0-0-1.sslip.io, but once Comodo (now Sectigo) got wind of that they revoked our key certificate within 24 hours.

Even though the "ssl" in the name no longer made sense, we never bothered to change it.

@cunnie cunnie closed this as completed Sep 16, 2023
@kumavis
Copy link
Author

kumavis commented Sep 16, 2023

thanks/

I was wondering if you could do a dns-auth cert as well but http-auth seems much easier

@cunnie
Copy link
Owner

cunnie commented Sep 17, 2023

I was wondering if you could do a dns-auth cert as well but http-auth seems much easier

Not easily. #24 is a good example of an ongoing discussion to address this.

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

2 participants