<p dir="ltr"><br>
Den 23 okt 2015 23:10 skrev "Philipp Winter" <<a href="mailto:phw@nymity.ch">phw@nymity.ch</a>>:<br>
><br>
> The Tor network uses self-authenticating names for onion services, e.g.,<br>
> 3g2upl4pq6kufc4m.onion. These onion domains are difficult to recognise<br>
> and remember, which is one reason why some onion service providers<br>
> started generating vanity domains. The idea is to keep generating key<br>
> pairs until the hash's prefix contains a desirable string. Facebook got<br>
> a pretty good one with facebookcorewwwi.onion.<br>
><br>
> Attackers have now started to impersonate onion services by generating<br>
> onion domains whose prefix resembles the original. An example is<br>
> DuckDuckGo's search engine:<br>
><br>
> Original: 3g2upl4pq6kufc4m.onion<br>
> Impersonation: 3g2up5afx6n5miu4.onion<br>
> ^^^^^<br>
> Users who encounter an impersonated onion domain might mistakenly assume<br>
> it's the original because they recognise the prefix. I worry that this<br>
> kind of phishing attack is particularly effective against vanity onion<br>
> domains because they might incentivise users disproportionately to only<br>
> verify the easily recognisable prefix.<br>
><br>
> As a result, I wonder if vanity onion domains raise more problems than<br>
> they solve. Should onion domain generation be made deliberately slow to<br>
> render vanity onion domains and phishing attacks impractical? Should we<br>
> provide browser-based tools to manage onion domains instead of treating<br>
> them like normal, memorable domains?<br>
><br>
> Thoughts?</p>
<p dir="ltr">They're representations of public keys. Treat them like all other representations of public keys. Don't expect the user to remember them exactly. Use bookmarks, phishing protected authentication (U2F / UAF), be careful with your sources. <br></p>
<p dir="ltr">- Sent from my tablet</p>