Gervase Markham | 3 Mar 2009 00:14
Picon
Favicon
Gravatar

Re: Work-around for Moxie Marlinspike's Blackhat attack

On 28/02/09 00:32, Jonas Sicking wrote:
> It'd be good to have a separate pref, network.IDN.blacklist_chars_extra,
> where users can add additional characters without having to worry about
> not receiving updates to the list we maintain.

If users have to add chars to this list manually, that's Really Bad - 
because most won't. What's easier - getting loads of users to modify 
this pref, or shipping an automatically-installed security update to all 
of them?

Gerv
Gervase Markham | 3 Mar 2009 00:13
Picon
Favicon
Gravatar

Re: Return of i18n attacks with the help of wildcard certificates

On 27/02/09 14:48, Boris Zbarsky wrote:
> It's not clear to me that the person who added the list even knew the
> page existed.

Neil added the list, and he wrote the second half of the page. So there 
was mutual knowledge. The list isn't documented on the page because, 
strictly speaking, it's not relevant.

> It seems like the right thing to do is to make the "this is the hostname
> of the site" ui somehow more prominent. Or possibly "this is the tld+2
> of the site" or something. Some UI mockups would probably help more than
> anything else.

We just turned hostname display UI for SSL on, according to The Burning 
Edge...

Gerv
Jean-Marc Desperrier | 3 Mar 2009 15:30
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

Gervase Markham wrote:
> [...]
> We just turned hostname display UI for SSL on, according to The Burning
> Edge...

This is a nice change, I found out about it on the burning edge too :-)

But, and as the link Eddy just reported shows, the attack is far from 
being only for SSL.

I think we should reconsider the options available to make the domain 
name more visible for http connexions.
What about a white version of the hostname display for http sites ?
Eddy Nigg | 3 Mar 2009 16:07
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

On 03/03/2009 04:30 PM, Jean-Marc Desperrier:
> But, and as the link Eddy just reported shows, the attack is far from
> being only for SSL.
>
> I think we should reconsider the options available to make the domain
> name more visible for http connexions.
> What about a white version of the hostname display for http sites ?

YEAH!

--

-- 
Regards

Signer: Eddy Nigg, StartCom Ltd.
Jabber: startcom <at> startcom.org
Blog:  	https://blog.startcom.org
Boris Zbarsky | 3 Mar 2009 16:51
Picon
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

Jean-Marc Desperrier wrote:
> But, and as the link Eddy just reported shows, the attack is far from 
> being only for SSL.
> 
> I think we should reconsider the options available to make the domain 
> name more visible for http connexions.
> What about a white version of the hostname display for http sites ?

Wait.  Why does the domain matter at all for non-SSL connections?  It's 
not like we have any guarantees against MITM here...

-Boris
Eddy Nigg | 3 Mar 2009 18:52
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

On 03/03/2009 05:51 PM, Boris Zbarsky:
> Jean-Marc Desperrier wrote:
>> But, and as the link Eddy just reported shows, the attack is far from
>> being only for SSL.
>>
>> I think we should reconsider the options available to make the domain
>> name more visible for http connexions.
>> What about a white version of the hostname display for http sites ?
>
> Wait. Why does the domain matter at all for non-SSL connections? It's
> not like we have any guarantees against MITM here...
>

If we train users to watch out for positive SSL indicators and warn 
before submitting any information I think this should not be necessary. 
However I could imagine a re-vamped UI where the actual domain name is 
more prominent and the real URL less important for the average user.

Something like this:

+----+-------------+
|    |             +-------------------------------------+
|SSL | DOMAIN.COM  |                  URL                |
|    |             +-------------------------------------+
+----+-------------+

The URL part might be only optional or hide and reappear on mouse-over.

--

-- 
Regards
(Continue reading)

Jean-Marc Desperrier | 3 Mar 2009 19:59
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

Boris Zbarsky wrote:
> Jean-Marc Desperrier wrote:
>> But, and as the link Eddy just reported shows, the attack is far from
>> being only for SSL.
>>
>> I think we should reconsider the options available to make the domain
>> name more visible for http connexions.
>> What about a white version of the hostname display for http sites ?
>
> Wait. Why does the domain matter at all for non-SSL connections? It's
> not like we have any guarantees against MITM here...

Well, we don't have the option to change the world, and in practice 
people just *do* send important login/password on http connections.

You do have a point though, maybe it's time to think if there's a way by 
which mozilla could push toward more use of https to protect sensitive data.
Boris Zbarsky | 3 Mar 2009 20:14
Picon
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

Jean-Marc Desperrier wrote:
> Well, we don't have the option to change the world, and in practice 
> people just *do* send important login/password on http connections.

But that's insecure no matter what we do with our UI, and we should NOT 
be doing anything that makes it look more secure.

-Boris
Florian Weimer | 4 Mar 2009 12:27
Picon

Re: Return of i18n attacks with the help of wildcard certificates

* Boris Zbarsky:

> Wait.  Why does the domain matter at all for non-SSL connections?
> It's not like we have any guarantees against MITM here...

Most users are not subject to MITM attacks, but they do receive all
kinds of URL lures.
Boris Zbarsky | 4 Mar 2009 14:36
Picon
Favicon

Re: Return of i18n attacks with the help of wildcard certificates

Florian Weimer wrote:
> Most users are not subject to MITM attacks

This may or may not be true given the prevalence of wireless networks 
out there...  we've had a number of reports of in-the-wild MITM attacks 
by wireless network operators.

> but they do receive all kinds of URL lures.

Yes, most of these are trying to phish sites that are normally SSL, so 
we should be making it very easy to tell when a site is not SSL or 
doesn't have the expected hostname over SSL.  Making non-SSL sites look 
more like SSL ones even by similarly highlighting the hostname is asking 
for trouble.

-Boris

Gmane