3 ms·

I love Sandstorm, but IMO, the requirement of a wildcard certificate is a small drawback in setting it up on my server. I know I can use sandcats.io but if I am

I love Sandstorm, but IMO, the requirement of a wildcard certificate is a small drawback in setting it up on my server. I know I can use sandcats.io but if I am using something like Sandstorm, I want complete control over my data, including domains. (I am now using sandcats though so there's that but I wish I could get a wildcard cert for free or from Let's Encrypt :)

kentonv 11y ago
I've talked to the Let's Encrypt people on several occasions about this. I think they will support wildcards eventually. The details are surprisingly hairy, though. In the meantime, we'll keep providing free certs under Sandcats. I too wish we didn't have the wildcard requirement. Unfortunately, same-origin policy being what it is, there's really no way for us to get away from the wildcard requirement without losing most of our security gains. You've probably seen this already but for others wondering about the details: https://docs.sandstorm.io/en/latest/administering/wildcard/ https://docs.sandstorm.io/en/latest/administering/wildcard/ And a sample of security problems that our security model (of which the wildcard is an essential part, since it enables fine-grained isolation) has helped protect against: https://docs.sandstorm.io/en/latest/using/security-non-events/ https://docs.sandstorm.io/en/latest/using/security-non-event... Thanks for using Sandstorm!
- tokenizerrr 11y ago
  Once the rate-limits for LE relax, what about on-demand renewal of a SAN certificate?
  - kentonv 11y ago
    Sorry, that won't work. Sandstorm needs a new hostname every time you open a document (that's a lost of hostnames), and to provide any CSRF mitigation it needs to be a secret (where anything you list on the certificate immediately becomes public knowledge). Be sure to read the FAQ in the doc: https://docs.sandstorm.io/en/latest/administering/wildcard/ https://docs.sandstorm.io/en/latest/administering/wildcard/

kentonv 11y ago

I've talked to the Let's Encrypt people on several occasions about this. I think they will support wildcards eventually. The details are surprisingly hairy, though. In the meantime, we'll keep providing free certs under Sandcats. I too wish we didn't have the wildcard requirement. Unfortunately, same-origin policy being what it is, there's really no way for us to get away from the wildcard requirement without losing most of our security gains. You've probably seen this already but for others wondering about the details: https://docs.sandstorm.io/en/latest/administering/wildcard/ https://docs.sandstorm.io/en/latest/administering/wildcard/ And a sample of security problems that our security model (of which the wildcard is an essential part, since it enables fine-grained isolation) has helped protect against: https://docs.sandstorm.io/en/latest/using/security-non-events/ https://docs.sandstorm.io/en/latest/using/security-non-event... Thanks for using Sandstorm!

tokenizerrr 11y ago
Once the rate-limits for LE relax, what about on-demand renewal of a SAN certificate?
- kentonv 11y ago
  Sorry, that won't work. Sandstorm needs a new hostname every time you open a document (that's a lost of hostnames), and to provide any CSRF mitigation it needs to be a secret (where anything you list on the certificate immediately becomes public knowledge). Be sure to read the FAQ in the doc: https://docs.sandstorm.io/en/latest/administering/wildcard/ https://docs.sandstorm.io/en/latest/administering/wildcard/