9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch smtp: ignore unrecognized certificates
Date: Mon, 20 Jul 2020 17:32:17 +0200	[thread overview]
Message-ID: <CAFSF3XNzBudBF1=kVx89Pw7e6_uWqzQq6rBKgbk0bX2HbPkOVw@mail.gmail.com> (raw)
In-Reply-To: <B85B65A6162E76DCA6BD621B5104C1B3@eigenstate.org>

> a problem everyone else seems to have solved.
you call that solved?!

i think it's the opposite, as it makes it worse giving people false
sense of security.

On 7/20/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
>> The problem is that if there is a chain, you need to trust the root you
>> finally end with. So whether this is a volunteers based C.A. or a
>> professional paying one.
>
> Yes -- it'd mean distributing the usual set of trusted root certs
> with the OS. Probably lifting /etc/ssl/cert.pem from a Unix box.
>
> It also sucks, but it's a problem everyone else seems to have solved.
>
>


  reply	other threads:[~2020-07-20 15:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aee5c8d2-ef2b-4ef2-8594-e6786cbd6e2e@sirjofri.de>
2020-07-19  9:43 ` Joel Fridolin Meyer
2020-07-20 14:05   ` [9front] " ori
2020-07-20 14:20     ` hiro
2020-07-20 14:26       ` ori
2020-07-20 14:46         ` tlaronde
2020-07-20 14:52           ` ori
2020-07-20 15:05             ` tlaronde
2020-07-20 15:09               ` ori
2020-07-20 15:32                 ` hiro [this message]
2020-07-21  6:55           ` cinap_lenrek
2020-07-20 16:18     ` cinap_lenrek
2020-07-20 17:16       ` Joel Fridolin Meyer
2020-07-20 22:00       ` Steffen Nurpmeso
2020-07-20 22:05         ` ori
2020-07-20 22:19           ` Kurt H Maier
2020-07-21 13:02             ` Steffen Nurpmeso
2020-07-20 22:07         ` ori
2020-07-21 13:46           ` Steffen Nurpmeso
2020-07-29  7:32             ` sirjofri+ml-9front
2020-07-29  8:04               ` hiro
2020-08-01 10:01               ` cinap_lenrek

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='CAFSF3XNzBudBF1=kVx89Pw7e6_uWqzQq6rBKgbk0bX2HbPkOVw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).