public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] This Connection is Untrusted: WAS: Firefox-10.0.1 fails to compile on x86
Date: Fri, 24 Feb 2012 11:33:01 -0600	[thread overview]
Message-ID: <CAEH5T2MDUjjzem5g_D+1n9wCSdfE_15ZR4iGSErKLqM1n_qOdQ@mail.gmail.com> (raw)
In-Reply-To: <4F47BE2A.6050202@orlitzky.com>

On Fri, Feb 24, 2012 at 10:43 AM, Michael Orlitzky <michael@orlitzky.com> wrote:
> On 02/24/12 02:45, Florian Philipp wrote:
>>
>> Let's not forget that whenever you are presented with that warning, it
>> could also be a man-in-the-middle attack. Therefore just clicking on
>> "Accept" on every site is about the stupidest thing you can do.
>>
>> I'm unsure how the warning looks when you have previously accepted a
>> normally untrusted certificate on that site and now it is different
>> (which could be an indication of MITM). I hope there is a big red flashy
>> warning but I doubt it.
>>
>
> Not if the certificate is "valid."
>
> The only sane way to handle certificates with parties you've never met
> (i.e. every website) is the SSH method: you accept that, no matter what,
> there's always going to be one opportunity for a man-in-the-middle
> attack. The first time you connect, you save the remote server's
> certificate. If it changes, freak out.
>
> The certificate patrol extension does this:
>
>  http://patrol.psyced.org/
>
> With it, self-signed certificates become more secure than CA-signed ones.

Thanks for the link. The MultiZilla extension way back in the
Netscape/Mozilla/Seamonkey 1.x days treated certificates like this:
you had to approve all certs the first time, even if they were from a
trusted CA and if it ever changed for any reason, it would refuse to
connect unless you approved the new cert.

It seems to me that's how it should *always* work, in all software
that uses SSL certificates, but I understand wanting to keep it simple
for non-technical users... but those are the very users most at risk,
probably the most likely to use hostile wifi networks (in my mind,
hostile is anything other than the router I control at my house).

Additionally http://perspectives-project.org/ or
http://convergence.io/ can help you in establishing the initial trust
and are an attempt at eliminating the need to trust CAs at all.



  reply	other threads:[~2012-02-24 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 22:59 [gentoo-user] This Connection is Untrusted: WAS: Firefox-10.0.1 fails to compile on x86 Mark Knecht
2012-02-23 23:11 ` [gentoo-user] " Nikos Chantziaras
2012-02-23 23:28 ` [gentoo-user] " Paul Hartman
2012-02-24  1:14   ` Mark Knecht
2012-02-24  3:01     ` Adam Carter
2012-02-24  7:45       ` Florian Philipp
2012-02-24 16:43         ` Michael Orlitzky
2012-02-24 17:33           ` Paul Hartman [this message]
2012-02-27 18:43             ` Florian Philipp
2012-02-27 19:32               ` Michael Orlitzky
2012-02-23 23:33 ` Willie WY Wong

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=CAEH5T2MDUjjzem5g_D+1n9wCSdfE_15ZR4iGSErKLqM1n_qOdQ@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --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