this post was submitted on 12 Sep 2024
105 points (97.3% liked)

Selfhosted

40696 readers
304 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
105
Paid SSL vs Letsencrypt (lemmy.ml)
submitted 3 months ago by [email protected] to c/[email protected]
109 comments fedilink hide all child comments
 

I'm curious what the benefits are of paying for SSL certificates vs using a free provider such as letsencrypt.

What exactly are you trusting a cert provider with and what are the security implications? What attack vectors do you open yourself up to when trusting a certificate authority with your websites' certificates?

In what way could it benefit security and/or privacy to utilize a paid service?

And finally, which paid SSL providers are considered trustworthy?

I know Digicert is a big player, but their prices are insane. Comodo seems like a good affordable option, but is it a trustworthy company?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 3 months ago (1 children)

I'd say they're actually easier, at least in my experience. Since wildcard certs use DNS-01 verification with an API, you don't need to deal with exposing port 80 directly to the internet.

[–] [email protected] 1 points 3 months ago (2 children)

Yes, it can be easier. But not every DNS provider allows API access, so you might need to change the provider.

(good luck with that in many enterprise scenarios).

[–] [email protected] 2 points 3 months ago

You can also delegate a subdomain to another provider with an API, but yes I see what you mean. Although I feel like getting port 80 open would be difficult as well in those situations.

[–] [email protected] 1 points 3 months ago (1 children)

You can use ACNE DNS. Just add the single record for acne dns and then you can the acne dns api to fulfill the challange.

[–] [email protected] 1 points 3 months ago* (last edited 3 months ago) (1 children)

Yes, if you do this ~~manually~~ it will work.

[–] [email protected] 2 points 3 months ago (1 children)

No, you can do this process to automate it.

[–] [email protected] 1 points 3 months ago

Sorry, I understood you wrong. You're right!