this post was submitted on 02 Jun 2023
16 points (100.0% liked)

Privacy Guides

16091 readers
262 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS
 

I vaguely remember reading something about leaking your private network setup if you used Let's Encrypt to generate your certificates.
Because of this when I installed my reverse proxy with caddy to handle my selfhosted home network I configured it to generate the certificates locally.
But this comes with the issue of the annoying warnings of the browsers plus being unable to connect to those devices/services which can't ignore it.

Am I being too paranoid? Is there any real concern about generating the certificates with Let's Encrypt for addresses which I don't intend to have outside my private network?

top 15 comments
sorted by: hot top controversial new old
[–] jonah@lemmy.one 7 points 1 year ago (3 children)

I don't see why you couldn't just get a wildcard certificate that doesn't include any hostnames, if you handle your traffic on a single Caddy reverse proxy anyways.

[–] krolden@lemmy.ml 2 points 1 year ago* (last edited 1 year ago)

Yup, wildcard with a TXT record of your reverse proxy local IP does it for me

[–] xradeon@lemmy.one 2 points 1 year ago

Yeah, solution is just to get a wildcard cert.

[–] pe1uca@lemmy.one 1 points 1 year ago

Ah, got it!
I'll look into it, AFAIK caddy autogenerates all certs for each site, so probably I'll have to manually create and import the wildcard one.

[–] edent@lemmy.one 5 points 1 year ago (1 children)
[–] ThreeHopsAhead@lemmy.ml 1 points 1 year ago (1 children)
[–] edent@lemmy.one 1 points 1 year ago (1 children)

Not sure what you mean? I don't use Cloudflare as a CDN.

[–] ThreeHopsAhead@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (1 children)

When I visit the link with JavaScript disabled I get blocked by a site stating "Please wait while your request is being verified..." and then nothing happens even though the actual site behind that screen displays fine without JavaScript.

[–] edent@lemmy.one 1 points 1 year ago (1 children)

Are you using a VPN? Can you share a screenshot? I don't use CloudFlare, but my host does block users which are from IP addresses which have previously been used for abuse.

[–] ThreeHopsAhead@lemmy.ml 1 points 1 year ago (1 children)

Tor Browser on Android. It happens on multiple circuits with different exits. Not an image by me, but it looks like this: https://global.discourse-cdn.com/cloudflare/original/3X/c/3/c38eaed81c96ac19e4fd5a69d4257445b391927e.png

[–] edent@lemmy.one 1 points 1 year ago

I don't support TOR, sorry. I got to much abuse from it and its users.

Wildcard cert both solves that, and makes life easier since you just have 1 cert for everything.

Depends on your risk profile, really. It'll technically leak out the DNS name your using internally in order to generate the cert. But, to get a cert from anything (if not wildcard) you'll have to do this if you don't want to spin up your own CA.

[–] kittyrunningnoise@lemm.ee 1 points 1 year ago

... in case you don't know: if it's for resources on a private home network, you can easily add the CA cert (i.e. the public key associated with the private key used to sign your certs) to your devices so that it's no longer unknown and the warnings disappear. I know this doesn't answer your question, but it's what I'd do instead of using letsencrypt for private services.

[–] JuvenoiaAgent@geddit.social 1 points 1 year ago

It leaks the names of your domains since info about all certificates are published. If that matters too you, a simple solution is to only generate and use a wildcard certificate (*.domain.tld).

load more comments
view more: next ›