PayPal Denies It Will Block Safari
Despite reports that PayPal may drop support for Apple's Safari browser because it lacks anti-phishing features, PayPal now says it ain't so. Though PayPal telegraphed displeasure with Safari last January, they're now unambiguous about their position: "We have absolutely no intention of blocking current versions of any browsers, including Apple's Safari, from our website."
So up-to-date Lynx, Links2, Dillo, etc are all perfectly acceptable?
Wowsa, that change is quicker than it takes the read the following:
Previous: "We know better than you do about what you should and shouldn't be using, so we will stop you possibly getting yourself into trouble."
Current: "Wow, there are so many of you that are quite happy to be wrong that we think you better be allowed to get yourselves into trouble."
My interpretation: Right or wrong, the masses will always win it seems.
Moved to http://soylentnews.org/. You are invited to join us too!
Real men FedEx cash.
they're now unambiguous about their position "We have absolutely no intention of blocking current versions of any browsers, including Apple's Safari, from our website."
It still sounds ambiguous to me. They could certainly mean "We will not target Safari by name, but we will just make you install a plugin that we know Safari can't use".
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
Spot on! And you can track where your money is.
*ducks*
they were going to deny certain browsers, I said the terrorists won.
I take it back. PayPal are the terrorists.
Now you have a little bar at the bottom of Safari that shows you the actual target of links.
http://Communityville.com - A free place for new and old neighborhood webmasters to hang out.
I closed my Paypal *and* eBay accounts when eBay said you HAD to accept Paypal in order to sell stuff and Paypal said they would hold payments for 21 days. Hated to see all that positive eBay feedback go, but I don't like being dicked around by corporate bozos.
There are so many other alternatives to Paypal that I don't see why people bother with it.
lynx https://www.paypal.com/ ...
SSL error:no issuer was found-Continue? (y) y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: cookie_check=yes Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: navcmd=_home-general Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: navlns=0.0 Allow? (Y/N/Always/neVer)y
# FINALLY there's a homepage. "Member Log In" is on the second page.
SSL error:no issuer was found-Continue? (y) y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
Refresh: 1 seconds
https://.../
SSL error:no issuer was found-Continue? (y) y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
www.paypal.com cookie: (censored) Allow? (Y/N/Always/neVer)y
Ok, if I'd hit "a" to those cookies, it would've been a lot better. And there are a fscking LOT of cookies.
Now, I haven't actually tried to do anything with it so far, but I suspect that it would, in fact, work just fine. It's curious that it doesn't like the SSL -- I suspect that's a problem with my version of Lynx, as Firefox and Konqueror don't give me any SSL warnings. But other than that, Paypal isn't doing anything to block Lynx, and it looks reasonably navigateable.
Don't thank God, thank a doctor!
Its a difference based on whether you have a Paypal cookie on your system. If you do, they push the paypal option, since that means you move money from one Paypal account to another and Paypal gets an interchange fee but doesn't have to pay anything. If you don't, they give the credit card equal billing, since they know that maximizes the odds of them getting a transaction, even if they have to kick back most of their interchange fee to the credit card.
Since your IE and Firefox cookies are not shared, my guess is that you haven't logged in on IE recently. Try logging in for both browsers then logging out and attempting a purchase. You'll get identical behavior.
Disclaimer: IANAEOP (I am not an employee of Paypal) but half my business runs through them.
Help poke pirates in the eyepatch, arr.
My suspicion is that when PayPal deals with browsers that are not "up to snuff", there will be differences in behaviour and additional back-end security measures that may not be used with "approved" secure browsers. But I doubt they will disallow any modern browser entirely.
The real question is what exactly does this do for "security". Anything that PayPal does on their end will have no affect on phishing sites. All current web browsers, regardless of how PayPal treats them, will function with phishing sites just fine. Any user that falls for a phishing scam is just going to think, "cool PayPal works again". I see no point in blocking a web browser unless for some ungodly reason, the phishers blocked those browsers too.
Burn Hollywood Burn
Common sense would say Why should we not block Safari ? It's up to the Safari developers to make it more secure, not PayPal to make exceptions because it's for "Mac" users.
I invite you to check Macworld discussion at
/usr/sbin/ocspd[1735]: starting (system.log)
http://forums.macworld.com/thread/98919?tstart=0
I have never seen a thing like that. Macintosh community hates them so much after that disastrous stupid statement that I STILL get new message alerts after 2 months as people keep commenting how stupid they are, Verisign bribed them, MS lapdog, eBay is scam.
This is a OS that loads ocsp on startup to check the SSL certs at core OS level:
Apr 22 09:07:29 quad
EV matters? How much it cost to a commercial site at size of Paypal? Does Paypal feel their consumers are insecure instead of using FREE data from community powered services like http://www.phishtank.com/ ?
Post a job listing for Cocoa/Carbon, Objective C developer. Cough some money and distribute your plugin. Don't use "No XUL" as excuse, it is easy to watch current URL on Safari. ICQ from 2003 can still read it.
Mail doesn't need to be fixed. Roll your cursor over any link and it will display a tooltip showing the URL to which the link would take you if clicked.
I would tend to agree that by default Safari isn't very helpful in this regard, but as previous posters already mentioned, the fix for Safari is simple: go to the View menu and select "Show Status Bar", or hold the Command key and press the / button. You only have to do this once, and Safari will keep this setting forever unless you turn it off.
the JoshMeister on Security
Perhaps PayPal realized what a phisherman's dream this would be: "Can't access your PayPal with Safari? Signup for PhishPal to get instant unrestricted access. We only need your email address, ssn, bank account number, credit card numbers and drivers license."
Joking aside, just teach people to type addresses in the address bar, and to check the address bar and status bar when they are entering sensitive information. Problem solved.
Win a signed Stephen Carpenter ESP Guitar from the Deftones: http://def-tag.com/?r=0008781
I'm wondering... how those Paypal folks could "block" your browser? Do they rely on your UserAgent? There must be some UASwitcher plugin for every browser out there, so you can easily bypass their filter... Any idea about how they filter you out?
You do make a good point, but the people that get hit most by phising are those that dont even know what a browser is, the kind of people that will phone you up with such useful complaints as "paypal is broken, what do i do?". These people will have a friend "fix paypal" like this, and wont even know what's happened.
The next most affected people are People who do understand thier browser but dont know about phising, this will not protect them, but hopefully this will cause apple to fix their defective browser where it matters instead of work on ACID3
The least affected people are the slashdot crowd that can argue about reading address bars and the have always checked the site for a padlock.
While not perfect this does help a lot of vulnerable users, at little cost to the rest
IranAir Flight 655 never forget!
I now that was a troll, but I may be able to offer some insight for thers reading this thread that may be helpful to future Mac admins out there and may save some hassle - which is really what being an admin is all about IMHO - saving my users hassle. If they have no worries, I don't get calls and can get back to updating my Mac build or quelling political infighting with some technical facts...
Safari pulls it's network and proxy info from the OS. FireFox does not - it has that set in a pref. The Mac laptops in our company network need proxy settings, DNS info, and a search domain entered to get at all the intranet goodness, as well as make it out to the cloud. In my image I create a WORK location and an AWAY location for the network. The work location has all the network settings for, well, you get the idea. This makes it simple for the user to go under the Apple menu to Location and select WORK or AWAY and still be able to connect to whatever they need to on site or off site. And even that takes a little training.
Unfortunately, FireFox doesn't support that. So the FireFox users would have to go into FireFox and navigate the prefs to find the proxy settings and manually enter the proxy settings in the network, and disable them when they are off site - in addition to choosing the work or away location under the Apple menu. For those that want to know how to do this, the info is on our Mac intranet site and the users are free to do it. But it's just a couple extra steps to remember to do and undo. And for most of my corporate users they could care less which browser they are using - as long as it gets them to the internets theys iz wantin.
So I have my Mac build with both Safari and Firefox set up and configured for work locations - even the status bar showing on Safari. But when they go offsite and just select the AWAY location, only Safari works. Those that know how to make FireFox work will do those extra steps. Those that don't, won't generally care, or will ask me or the help desk and get refrenced to the intranet site for details on how to get it working.
I hope that proves useful for any other Mac admins out there facing the same issue. If you have a better solution, please share it.
http://Communityville.com - A free place for new and old neighborhood webmasters to hang out.