Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Inside Safari 3.2's Anti-Phishing Feature

Posted by kdawson on Tue Nov 25, 2008 01:23 PM
from the just-tell-us dept.
MacWorld is running a piece from MacJournals.com's for-pay publication detailing how the Safari browser's anti-phishing works. The article takes Apple to task for not thinking enough of its users to bother telling them when Safari sends data off to a third party on their behalf. For it seems that Safari uses the same Google-based anti-phishing technology that Firefox has incorporated since version 2.0, but, unlike Mozilla, tells its users nothing about it. "Even when phrased as friendly to Apple as we can manage, the fact remains that after installing Safari 3.2, your computer is by default downloading lots of information from Google and sending information related to sites you visit back to Google — without telling you, without Apple disclosing the methods, and without any privacy statement from Apple."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Petersko (564140) on Tuesday November 25 2008, @01:27PM (#25889115)
    In Apple's defense, they've never promised to do no evil. Their goal is to instill such unswerving devotion in their customer base that when they actually do some evil, it's here and gone in the news, and nothing has to change.

    So far, so good.
    • It's actually much simpler: Apple decides things for you.

      Good or evil, what's actually going on here is that Apple has decided that the Best User Experience (TM) will be best served by you surrendering personal information to Google -- that the benefit of privacy is far outweighed by the risk of phishing.

      Kind of like how Apple decided that the benefits of being able to install any software you want on a device (iPhone) are far outweighed by the risks of you installing something harmful.

      And for what it's worth, when you agree with Steve Jobs on the way things should be done, it's actually pretty amazing. Safari isn't a bad browser.

      But when you disagree with Steve Jobs, you have no recourse other than to suck it up or stop buying Apple products.

  • by nweaver (113078) on Tuesday November 25 2008, @01:31PM (#25889173) Homepage

    The google service is designed to minimize privacy leaks. It downloads a coarse-hashcheck database (so Google learns nothing). And then if something hits, it queries a detailed hash.

    So unless you get a match on the coarse-hash database, Google learns NOTHING. And google only learns a hash if it matches, which is not very useful, AND google doesn't store this information unless it is a match with their detailed database.

    • by Petersko (564140) on Tuesday November 25 2008, @01:37PM (#25889247)
      "The google service is designed to minimize privacy leaks. It downloads a coarse-hashcheck database (so Google learns nothing). And then if something hits, it queries a detailed hash."

      The problem is the lack of disclosure.
      • Apple isn't a very open company anyways. There is probably policy that it is better to say too little then too much. Do you really expect there will be a team of lawyers for every new update that comes out. Even a big company the size of Apple having every version be legally verified would sink it.

      • The problem is the lack of disclosure.

        I'm going to play devil's advocate for a moment and point out that such disclosure is getting harder and harder to comply with. Especially when the web is seen as a collection of cloud services. Should that piracy map viewer posted yesterday disclose to every user that they will connect to Google Maps for map data? Does every website disclose that you are downloading ads from Google or Doubleclick before you visit? Does your favorite web forum notify you that you'll be connecting to Youtube when users post videos?

        Those examples convey far more sensitive information than this anti-phishing technology. Yet we don't even bat an eye. In fact, we praise them for such useful extensions to their services. Should web browsers thus play by different rules and be required to notify the user of a non-existent violation of privacy before they do something useful?

        I'm not saying that some people don't feel slighted by this. I am saying that the web is evolving in ways that have already made this the norm rather than the exception. If you do feel slighted and wish to be excepted, you're probably going to have to get used to reconfiguring your browser in the same way you install adblock or flashblock.

        • Re: (Score:2, Interesting)

          Don't all Google ad-blocks have 'ads by Google' on them? And I do believe all YouTube videos viewed off-site have the YouTube watermark. Plus, Google Maps mashups tend to have 'Google Maps' in the bottom right corner.
          • Don't all Google ad-blocks have 'ads by Google' on them?

            Which would be after you give your information to them. Most other ad agencies don't even go as far as that!

            And I do believe all YouTube videos viewed off-site have the YouTube watermark. Plus, Google Maps mashups tend to have 'Google Maps' in the bottom right corner.

            Same thing. You've already connected to their servers and given up your info. Just because there are logos to promote brand recognition there, doesn't mean that you consented to give up your info to a third party or received disclosure that it was going to happen. Google Maps even goes so far as to give you a Terms of Use link *after* you've engaged their services! *gasp!*

            I guess the question for you is: Would you feel better if the antiphishing technology had a "powered by Google" logo on it when it found a dangerous site? If so, I'm sure that's something that Apple would be willing to add. It won't do anything to better protect your privacy, though. It will merely give you a warm and fuzzy feeling.

            • Re: (Score:3, Insightful)

              Even learning after the fact is better than not being told that the transaction is taking place at all.
              • Glad you feel that way. I'll get a few post-event disclosures out of the way then:

                1. Your IP address, browser, operating system, installed plugins, and physical location were logged by Google Analytics as soon as you hit Slashdot.

                2. If you don't have adblock installed, your browser contacted doubleclick.net when you visited Slashdot and uploaded the unique id assigned to your browser. If you did not have a unique id, one was assigned to you. Additional information such as the site you are visiting, your browser, your plugins, your geographic location, and other information may have been collected during this transaction.

                Hope that helps!

        • Will I agree with you that this is a pointless argument I would say the difference between this and the examples you list is that it's an application on my desktop which is sharing the information. Not two website which have no relation to my computer or the information stored therein.

          It still think people will complain just because they need something to complain about to get noticed an feel important. They will scream slippery slope and wave there arms never realizing that there is no slope....it's a mi

          • Re: (Score:3, Informative)

            Will I agree with you that this is a pointless argument I would say the difference between this and the examples you list is that it's an application on my desktop which is sharing the information. Not two website which have no relation to my computer or the information stored therein.

            It still think people will complain just because they need something to complain about to get noticed an feel important. They will scream slippery slope and wave there arms never realizing that there is no slope....it's a minefield and we are all wearing rollerskates.

            I have the feeling you don't know how a browser works - it's not Slashdot that is sending the data, it's your browser. And if you are so paranoid about your privacy, you shouldn't be using any browser.

        • I'm going to play devil's advocate for a moment and point out that such disclosure is getting harder and harder to comply with.

          "Attention: By default, Safari now downloads a database from Google and connects back to Google to verify whether sites you visit in your browser are rated as malicious by Google. If you would like to opt out of this feature, uncheck this box: [x] Use Google's malicious site checking service."

          Just banged out a draft version for ya. Took me all of about 1 minute, and I don't e

      • The problem is the lack of disclosure. That may be, but the truth is that 99.99% of users in general wouldn't have a clue what to do with that information.
      • The problem is the lack of disclosure.

        Firefox has disclosed jack shit to me. So where's your problem with that?

        • "Firefox has disclosed jack shit to me. So where's your problem with that?"

          I'd have the same problem with them. Of course, I use neither Safari nor Firefox.
          • Re: (Score:3, Insightful)

            So when Mozilla puts something in the license, they are disclosing it, and when Apple puts it in the EULA, they are hiding it. Thanks for clearing that up.
    • I had a look through my settings, in 2.0 IRCC there was an option to download the list instead of checking as you browse, as i cant find the option anymore I'm quite disappointed that Mozilla have effectively compromised my privacy OR left me undefended.

      • Re: (Score:3, Informative)

        You've got it backwards. There is no longer an option to check as you browse and the check against the local list has always been the default.

  • I know Apple is based in the USA, with notoriously weak data protection laws, but over on this side of the pond distributing personally-identifiable information to a third party without explicit consent is a criminal offence. I wonder how close to the line this comes, or if it actually crosses it. I wasn't asked to agree to a new version of the EULA when I installed Safari 3.2 (I did it through the terminal, so maybe you are when you use the graphical update client?) and so I haven't even given implicit p
    • by negRo_slim (636783) on Tuesday November 25 2008, @01:56PM (#25889507) Homepage

      but over on this side of the pond distributing personally-identifiable information to a third party without explicit consent is a criminal offence.

      Sorry I'm less than enthusiastic at your privacy laws considering there's a camera on every corner in your country, watching the citizenry.

      • That's just the UK though, the rest of us aren't quite so quick to use Orwell's books as a "how-to" guide...

        /Mikael

      • there's a camera on every corner in your country

        No there isn't.

        In the UK there might be, but we don't know that your parent poster is from the UK.

        I'm from Denmark, some other country on the same side of the pond as the UK, and we don't have any cameras filming the streets.

        I haven't read our data protection laws as closely as our copyright laws, but my general recollection is that we don't exactly let everyone talk about who we are. I was recently looking at switching to a free* phone company (*first 50 minutes and 50 SMSes every month, more than enough

      • Well I have two comments to make to that...

        I have walked around my local town and I have only seen 4 cameras. They are not as prolific as you seem to think that they are. Perhaps there are areas of major cities where they are on almost every street corner, but not where I live.

        Secondly, do you imagine that these cameras are sending personally identifiable information to third parties? I don't. The cameras are used by the police for crime detection, prevention and/or deterrence. I support their use beca

    • I know Apple is based in the USA, with notoriously weak data protection laws, but over on this side of the pond distributing personally-identifiable information to a third party without explicit consent is a criminal offence.

      As I understand it, it sends a hash, not personally identifiable information.

    • I agree that this is a bad idea, but the information A) is not personally identifiable -- the specificity is at best an IP address and B) isn't being provided to Apple, and therefore Apple isn't providing it to anyone.

      If you wanted to argue with B) I think you'd have to make MS liable for every virus that uses the built-in TCP/IP and vCard libraries to query your address book and send off your personal information -- after all, the virus was using both libraries as designed and provided by MS.

    • Re: (Score:3, Informative)

      The key is "personally-identifiable". What Apple is sending is not. They are sending a hash of a page. All they are doing is taking something you just downloaded, scrambling it up and sending it back to the web.

      If you are truly worried about people finding out what sites you are browsing then you need to worry a LOT about DNS servers. DNS server know your IP address and the name of every site you click. How would you know if the DNS server is logging your queries?

      • The feature list says "anti-phishing technology." It says nothing about how the technology is implemented or that it sends data to a third party.

  • Remember, the people who designed the Internet (incorrectly) assumed that all computers on the network would be trustworthy, so the rules are pretty loose.

    C'mon, Macworld is better than this. Okay, the article is critically reviewing the anti-phishing feature, but the writer seems to have a bone to pick and in order to post an emotionally charged article, takes things one step too far.

    The internet was intentionally designed, itself, not to have a centralized authorizing body for each and every PC and server on the planet. It's decentralized on purpose. When a so called journalist writes something like this, I have a problem, because to me it's just pandering to the security freaks. It's a bit off topic, but I also have a problem reading the rest of the article because it makes it hard to trust what the guy has to say. There's probably good facts in the article, and if there's a problem Apple should be criticized, but I can't possibly continue reading when I see something stupid like this.

  • Just use Firefox and be done with it, while all browsers have their faults (and features) Safari offers nothing unique (IMO) and Firefox most likely has a bigger team of coders behind it.

    I use Firefox on Ubuntu, XP, and OS X Leopard so I have continuity/usability across the board, and that is what sells me on open source.

    • Re: (Score:2, Informative)

      Just use Firefox and be done with it...

      Um, you realize that Firefox uses the exact same anti-phishing technology, right? If you prefer Firefox, that's great but as far as this particular issue goes the difference is disclosure, not implementation. I like Firefox, but Safari is faster and less of a CPU and memory hog on OS X in my experience. And the integration is better - so I'll stick with Safari (although I skipped 3.2 because of all the crash complaints and I use FF for serious HTML/DOM/JavaScript hacking.)

    • Just use Firefox and be done with it, while all browsers have their faults (and features) Safari offers nothing unique (IMO) and Firefox most likely has a bigger team of coders behind it.

      And yet they use they use the exact same feature you are so pissed about it being in Safari.

        • Read TFA -- or at least TFS, FFS.

          This article is about an anti-phishing feature in Safari that compromises your privacy.

          Your solution is to switch to Firefox, which has the exact same feature enabled by default.

          Aside from sheer Firefox fanboyism, what's your point?

  • by Animats (122034) on Tuesday November 25 2008, @02:39PM (#25890087) Homepage

    Our AdRater plug-in has similar privacy issues. It's a plug-in that "phones home" to get information about the advertisers whose ads appear on a site. Here's what we tell users:

    AdRater "phones home", but tells us as little as possible. AdRater sends the domain name associated with each advertisement you see to SiteTruth. Thus, we can tell what advertisers have reached you, but cannot tell what web pages you have been viewing. We can't tell if you click on an ad. AdRater does not use "cookies" or any other user identifiable information other than your current IP address.

    If we change any of this, the changes will not take effect until you download and install a new version of AdRater.

    AdRater does not rate ads on secure pages, so no information about a secure page is ever sent to our servers.

    Now that wasn't hard, was it?

    For really technical users, we publish the API AdRater uses [sitetruth.com], so you can check to see that we're telling the truth about what data goes back and forth.

      • It does, however, present it in a non-technical way first:

        AdRater "phones home", but tells us as little as possible.

        For many users, that says it all.

        AdRater sends the domain name associated with each advertisement you see to SiteTruth.

        A domain name is pretty common knowledge. Even if it isn't, now you know some information is going to something called SiteTruth.

        Thus, we can tell what advertisers have reached you, but cannot tell what web pages you have been viewing. We can't tell if you click on an ad.

        Again, non-technical.

        It seems like a non-technical user could read this and understand enough to decide whether or not they need to care -- and if they need to care, they can ask for help understanding it. Us technical users are grateful that all the relevant information about IP addresses,

  • by $criptah (467422) on Tuesday November 25 2008, @04:41PM (#25891955) Homepage

    I fail to see how this is a big deal. Did you read the article? If so, you would not panic as well.

    First of all, everything is transported in hashes. You do not compare the actual URLs that customers visit, only the hashes. Google has no actual links that indicate the banks that you use and the pr0n sites you have browsed. Only hashes.

    Also, this is a configurable option. Apple does not force you to use Google. Apple does not force you to use this feature. I think it would be easier if Apple has explained this feature in the release notes to a greater extent and if users had to accept some sort of a license agreement when enabling this feature. Nothing else beyond it.

  • by adavies42 (746183) on Wednesday November 26 2008, @01:57AM (#25896629)

    to repeat what i said on the macworld article's comment board,

    sudo dscl localhost -create /Local/Default/Hosts/safebrowsing.clients.google.com IPAddress 127.0.0.1

    (or do the obvious with /etc/hosts if you're still running tiger (not that i know if safari 3.2 is available for tiger....))

    • Re: (Score:3, Informative)

      First off, because it drives me nuts, it is "couldn't care less". (Cue picking on grammar errors in this post. Maybe I'll drop a couple in intentionally!)

      Secondly there is adblock (and flashblock) for Safari in the form or SafariBlock [google.com], or if you don't care for Input Managers there's always things like GlimmerBlocker [glimmerblocker.org] which is a local HTTP Proxy which will block ads (and flash and do other fancy things) across the whole system and not just one browser.

    • Every time apple upgrades Safari, they disable my brilliant adblocker, Pithhelmet, and so I wait for the developer to hack it out again... Maybe I won't upgrade. Maybe my next mac will be running on mixed pc hardware. I'm strongly considering that...

      Just install Firefox with adBlocker.

    • Re: (Score:2, Informative)

      Have you tried SafariBlock? http://fsbsoftware.com/index.html [fsbsoftware.com] Works pretty well for me.
    • I bailed on pith-helmet right after 10.5 due to it always being behind the times. (I even paid for it). I would get a pith-helmet update just in time for a new safari release which would break it.

      SafariBlock is the way to go IMHO.

      Sheldon

    • A lot of you seem to love Apple

      I use Safari because it's well integrated with OS X. Firefox isn't, and Camino (which I use by preference) has a couple of bugs that are supposed to be fixed Real Soon Now that make it lock up behind a proxy and don't let me disable Apple's stupid insecurity dialogs.

      I also use Safari and Camino because they don't use XUL the way Firefox does. I don't trust the security model for XUL nor the technique Firefox uses for the XUL installer, XPI. And in fact there's been at least one XPI-related vulnerability (quickly patched, but it shows that the class of problems I'm concerned about are real).

      This doesn't mean I love Apple, or that I think the folks on the Camino team are cooler than the ones on the Mozilla team. This just means I'm more interested in the best tool for the job than where it comes from.

        • Re: (Score:3, Interesting)

          Webkit's really not Cocoa, but I guess it's not politically correct to say that it's Carbon. :)

          Integration with OS X is a lot easier for Cocoa applications, of course. It's harder if you're using code not written in Objective C, as Safari and Camino both do (Webkit and Gecko), but it's certainly possible... as both Safari and Camino demonstrate.

          Safari and Camino use the keychain for passwords. Firefox doesn't.
          Safari and Camino use the OS X proxy settings. Firefox doesn't.
          Safari and Camino integrate with Ser

      • This quote from the summary struck me as odd:

        The article takes Apple to task for not thinking enough of its users to bother telling them when Safari sends data off to a third party on their behalf.

        I don't really want to be bugged every 5 seconds that my computer is doing something on my behalf. Those sort of "features" are what I dislike about the Windows operating environment. Maybe it is just me, but there is a definite sweet spot for the trade-offs of security versus convenience. To say what you said in a more positive tone would be that Apple seems to lean towards convenience.

    • I don't see this pattern of thinking in our industry changing

      The important question here is of course this: who is making the choices?

      Who decides that this is the way it will be? I can only imagine that Debian's popularity-contest was conceived by someone who knows how to write code, and presumably cares about privacy in relation to computers. They may not have the same values as me, but I think it's on their radar. It's probably also written primarily by the person conceiving it.

      I'm still in school (although I've dipped my toes in the non-free real world for a ye