[flagged]
Lmao what so you think the LLM is trained on? And the data set is frozen in the past because LLMs are polluting the web with generated garbage.
[deleted]
Search.chatgpt.com domain and SSL cert have been created
21–30 of 126 posts
Re: Search.chatgpt.com domain and SSL cert have been created
#22[flagged]
ChatGpt will happily sell you snake oil wrapped in your favourite flavor of BS
Re: Search.chatgpt.com domain and SSL cert have been created
#23Isn't that conflicting with their microsoft deal?
Probably uses Bing to an extend.
Re: Search.chatgpt.com domain and SSL cert have been created
#24Re: Search.chatgpt.com domain and SSL cert have been created
#25Re: Search.chatgpt.com domain and SSL cert have been created
#26Re: Search.chatgpt.com domain and SSL cert have been created
#27I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…
Let’s encrypt and similar ACME compliant services allow you to get wildcard certs through their DNS-01 challenge.
Re: Search.chatgpt.com domain and SSL cert have been created
#28I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…
This would be so great. It also just mirrors the DNS trust model nicely, which is what’s used for X.509 trust anyway by most CAs.
Re: Search.chatgpt.com domain and SSL cert have been created
#29I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…
The point of certificate transparency is to have a public audit log of every certificate issued. Even if you had your own CA, you would be obliged to report every certificate you issue to the CT. This is a feature, not a bug.
Re: Search.chatgpt.com domain and SSL cert have been created
#30I'm taking this opportunity to once again ask for the widespread adoption of the Name Constraints extension in x509, and subsequent roll-out of constrained intermediate CA certs signed by a publicly trusted root. Would be so convenient to have an intermediate CA cert constrained to *.my-name.com to avoid situations like this. Being forced to either use a private PKI infrastructure or using wildcards to not leak host…
Let’s encrypt and similar ACME compliant services allow you to get wildcard certs through their DNS-01 challenge.
A wildcard cert is an unnecessary risk, though.
Just because I trust a server to hold the cert for preview.example.com doesn’t mean I’d want it to be able to pose as prod.example.com, for example.