Re: Avoiding HTTPS pitfalls [was: Re: Moxie Marlinspike]

To: or-talk@xxxxxxxxxxxxx

Subject: Re: Avoiding HTTPS pitfalls [was: Re: Moxie Marlinspike]

From: Fran Litterio <flitterio@xxxxxxxxx>

Date: Mon, 23 Feb 2009 15:04:27 -0500

Delivered-to: archiver@xxxxxxxx

Delivered-to: or-talk-outgoing@xxxxxxxx

Delivered-to: or-talk@xxxxxxxx

Delivery-date: Mon, 23 Feb 2009 15:04:30 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=zmnwoIOmtVF7fKR/TLWdhgxHbFsbYSQbGjbFuOzzlqc=; b=V8zqmolSl2wVifd+TGueJ5gaA2vZrDHVBARti22AlP0WhwTXQijBsUojNSW9WoSQON NmEjv1bZSu//y6Rx9GXll4z6UEW0ZH/PR5boHV3c+4f2ExKGkbnBzoU6zGNajov9zjgk +TlfgPCPfqSw4htnZdK+KZgnqZBkv0Z1B/oRY=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Wd229CFlcSJO0J6dG2dZ7EZo9251ttvkgrGBsb+JmbPyaH0TqvJrrzz58dRsvgvBI9 vUcWGnVYg8THzN7MJDtxDzCOJf2c2ZNxRWuMwdBiTUYmQsO93csKvbhopnnH5/JnU0I6 sd9ngZlnFDFHYp+c8OM49Vns1xEEwLfLDvgFk=

In-reply-to: <4ef5fec60902231119s2cccd1bcwdfb3313046b2a988@xxxxxxxxxxxxxx>

References: <4ef5fec60902231119s2cccd1bcwdfb3313046b2a988@xxxxxxxxxxxxxx>

Reply-to: or-talk@xxxxxxxxxxxxx

Sender: owner-or-talk@xxxxxxxxxxxxx

coderman wrote:

i always recommend two things when using HTTPS over Tor:
- install the petname toolbar. this will also notify you if some
rogue CA is suddenly signing the google.com certs, for example, not
just that encryption isn't used.

In http://www.mozdev.org/pipermail/petname/2009-February/000019.html, Tyler Close, the author of the Petname add-on for Firefox says that Petname no longer binds the chosen petname to the SSL certificate but to the origin (URL scheme, hostname, port number). He references Collin Jackson's research on origin granularity in browsers at http://crypto.stanford.edu/websec/origins/ as justification for this change.

This is ok, but I'd also like to be alerted when the certificate changes for a site that I regularly visit. If I visit https://sometime.com/ and an attacker steals or cache-poisons that domain name using a valid SSL certificate (but not the one from the real owner of the site), then Petname can't help me.
--
Fran