public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: Letsencrypt (was Re: [gentoo-user] app-misc/ca-certificates)
Date: Tue, 01 Jun 2021 13:17:12 +0200	[thread overview]
Message-ID: <2212846.ElGaqSPkdT@iris> (raw)
In-Reply-To: <20210601104447.D7EA282B8F89@turkos.aspodata.se>

On Tuesday, June 1, 2021 12:44:47 PM CEST karl@aspodata.se wrote:
> BillK:
> ...
> 
> > And another "wondering" - all the warnings about trusting self signed
> > certs seem a bit self serving. Yes, they are trying to certify who you
> > are, but at the expense of probably allowing access to your
> > communications by "authorised parties" (such as commercial entities
> > purchasing access for MITM access - e.g. certain router/firewall
> > companies doing deep inspection of SSL via resigning or owning both end
> > points). If its only your own communications and not with a third,
> > commercial party self signed seems a lot more secure.
> 
> ...
> 
> You can use https://letsencrypt.org/ instead of a self-signed cert:
> 
>  Let's Encrypt is a free, automated, and open certificate authority
>  brought to you by the nonprofit Internet Security Research Group (ISRG).
> 
> It was pretty simple to get it to work with
>  https://github.com/diafygi/acme-tiny

It's not that easy to do it with internal-only systems as Let's Encrypt 
requires the hostname to be known externally.
And there are plenty of devices you do not want the whole internet to know 
about.

--
Joost




  reply	other threads:[~2021-06-01 11:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29  1:08 [gentoo-user] app-misc/ca-certificates zcampe
2021-05-29  6:26 ` Walter Dnes
2021-06-01  4:45   ` J. Roeleveld
2021-06-01  5:15     ` William Kenworthy
2021-06-01 10:44       ` Letsencrypt (was Re: [gentoo-user] app-misc/ca-certificates) karl
2021-06-01 11:17         ` J. Roeleveld [this message]
2021-06-01 11:40           ` Michael Orlitzky
2021-06-01 12:02             ` Peter Humphrey
2021-06-01 12:16               ` Michael Orlitzky
2021-06-01 12:24                 ` Peter Humphrey
2021-06-01 13:22                 ` Rich Freeman
2021-06-01 13:17             ` karl
2021-06-01 13:20               ` karl
2021-06-01 13:17           ` karl
2021-06-01 11:59       ` [gentoo-user] app-misc/ca-certificates Adam Carter
2021-06-01 13:29         ` Rich Freeman
2021-06-02  1:13           ` William Kenworthy
2021-06-03  9:06           ` Adam Carter
2021-06-01 21:25       ` Grant Taylor
2021-06-01 21:38         ` Michael Orlitzky
2021-06-02  1:51           ` Grant Taylor
2021-06-02  7:21             ` J. Roeleveld
2021-06-02 20:22               ` Grant Taylor
2021-06-02  7:48             ` Fannys
2021-06-02 20:23               ` Grant Taylor
2021-06-01 22:28     ` Fannys
2021-06-02  7:23       ` J. Roeleveld
2021-06-01 21:05   ` Grant Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2212846.ElGaqSPkdT@iris \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox