Quote:
Originally Posted by Filark
I read about the Dolphin privacy/security problem on Ars Technica a couple of days ago: http://arstechnica.com/gadgets/news/...or-android.ars. I thought the fact that the data was transferred in plain text was a big part of the problem. Very happy that they stepped right up with a solution. 
I tried Googling my name . . . spooky!  Luckily for me none of the links that popped up were really about me, just my namesakes in other cities.  |
Dolphin was transferring web requests in plain text to a Webzine proxy server to see if a cached paged existed in an attempt to speed up browsing. Any secure socket connections would have resulted in no match to cache pages on the server and passed on to the secure website.
What amazes about each and every one of these stories is peoples inability to read. Dolphin 6.0's VERY short EULA is only five sentences long and it clearly points out that the browser uses a background agent and will collect the user experience data to aid in future improvements. The EULA is written in very simple language, but apparently for some people it is still too difficult to comprehend or they ignore it. It's clear that no personally identifiable information is being tracked because in step 2 of the EULA it gives you an opportunity to setup an account with Dolphin and enter an e-mail address, which you can opt to skip.
While I do agree Dolphin should have allowed an opt out (technically they did because you can decline the EULA), the lesson here is learn how to READ something before you agree to it. Ignorantia juris non excusat.