And I thought, why the heck would one phone be issuing so many concurrent IMAP connections. Oh my naiveté.
"[iOS 7] opens many IMAP connections at once for searching each folder concurrently. We’re not sure on the upper bound on the number of connections it will make, but saw at least 10 in one case."
I already know that Yahoo! sells the email addresses of the people I exchange even one email with to LinkedIn and I am repulsed by this. LI then turns around and offers them as connections. I should note I am always logged out from LI to prevent even more evil from them. LI is just evil and should be eradicated.
Their iphone app used to slurp up your data without authorization: http://arstechnica.com/apple/2012/06/your-iphone-calendar-is...
Furthermore:
LinkedIn: The Creepiest Social Network
https://news.ycombinator.com/item?id=5680680
LinkedIn opts 100 million users into sharing information with ads
https://news.ycombinator.com/item?id=2872030
LinkedIn is Evil
[0] http://www.zdnet.com/blog/btl/6-46-million-linkedin-password...
Also, while rare, the client could theoretically be using something like kerberos to authenticate, even over tls. The password exchange is secret, but the data contents would not be. I don't think the iphone supports kerberos, though.
(All this is not proof that they aren't your storing password, just that it's feasible for linkedin to merely pass it through. And possible, though not probable, for them to never even see the password.)
Encrypting user credentials in JS is probably even worse than parsing HTML with regular expressions: http://stackoverflow.com/questions/1732348/regex-match-open-...
Just send it in cleartext, but over properly verified https.
That being said, look at something like blockchain.info.
It adds javascript security on top of https, and for (what seems like) excellent reasons.
To avoid the "hash is a plaintext password" problem you save double-hashed passwords to your database, once in the browser and once on the back-end, twice on the back-end if JavaScript was disabled in your user-agent.
Of course that doesn't solve the problem above, but it still ought to be common practice.
However, for traditional IMAP/SMTP servers your point is well taken. They must store your credentials in a restorable state, which, however carefully you do, has difficult security implications.
Here's how Mint.com stores your banking credentials: https://www.quora.com/How-do-mint-com-and-similar-websites-a... I assume LinkedIn Intro would be using a similar technique.
Part of being a semi-decent citizen of the internet is also not encouraging users to give third parties their credentials
It is a neat hack. I'd love this if it was "here's how we integrate LinkedIn into our email clients internally". It is novel and it does use CSS in weird and new ways. It should also not be a shipping public product. MITM is bad shit.
It seems like they're aware of this but it's hardly their responsibility to avoid building a hack such as this just because Google are the only provider to allow IMAP access with OAuth. If more e-mail providers would allow such authentication, I'm sure LinkedIn would be happy to extend the support.
Is that so? "Fsck the world, we got a business to run?"
LinkedIn: moving their content to your e-mail address.
G-mail/Yahoo: Duplicating your content.
LinkedIn: Manipulating your content.
G-mail/Yahoo: E-mail providers.
LinkedIn: Social media provider.
G-mail/Yahoo: uses protocols as intended to provide service.
LinkedIn: uses hacks to provide service.
G-mail/Yahoo: No risk of compromising devices.
LinkedIn: Extreme risk of device compromise. Intentionally circumvents device security features. Multiple potential points of security breach (at proxy server, at web server, through rendering engine).
No comparison, really.
The only relevant difference is security/privacy, in which Google may be more trustworthy but even that is debatable, regardless of which side of the debate you land on.
This, like dd+nc, has some practical concerns such as security, but that doesn't mean it isn't creative and interesting.
It only becomes problematic when you consider that the user is getting themselves into a situation that they do not fully understand and potentially cannot easily back themselves out of.
With drugs that have a high potential to cause harm, we typically force the consumer to consult a professional before allowing them to proceed. Tech is still in the era of patent medicines.
There's no such thing. Email breaks the concept of email security.
LI, Google and Facebook have always wanted your third-party email credentials for Friend Finder-style features. The only difference is that this time we cannot even hope that they delete them after logging in once. Security-wise, it's all the same.
How is that even close to a valid response to someone that's exercising critical thinking?
Access to this many passwords is a threat even if my password is not one of them.
Finally, it may be opt in, but are they going to explain to the user that they get to keep a password for an account to which they have no legitimate right?
I doubt they have a warning when you install this "This is going to let us read all your emails AND the emails of people who communicate with you (without their consent)
...oh yes, and get your username / password for your email accounts"
And if I am communicating with someone who installed this hack then I certainly didn't opt-in.
This is extremely important and getting lost in the noise.
Do people find the technical details interesting despite the privacy concerns?
Either way, congrats to Martin, Sam and others on the launch. Getting something out the door to such a wide audience after working on it for over a year must be quite a challenge.
Next thing: store your S/Mime private keys on linked in servers to enable the feature also for encrypted mails...
I think LinkedIn should not offer every feature that's technically possible. Things should stay within reason, and some things should not be offered, especially not to non-savvy users.
The user has to install the profile as trusted. There is no mechanism for auto installing a profile. Similar to TestFlight and the profile you install to use that.
At first I'm thinking, oh, I wonder how they convinced Apple to let them use some private APIs, and then... curiosity turns to revulsion as soon as I saw that proxy diagram. Good god... LinkedIn MITM IMAP. That is truly terrifying.
How would you even go about installing that on the user's phone? Oh, that's in there too... they ship a 'configuration profile' which adds a new email account, so your password is leaving the device in cleartext and being used to create the profile server-side which is then shipped back to the phone and installed, how exactly?
This just gets worse and worse if I understand correctly... I'm surprised that configuration profiles can be shipped to an arbitrary device from a third party this way without the user manually installing LinkedIn's certificate as trusted. In other words, it should be a lot harder to "Accept" these profiles outside an enterprise setting, because it sounds exploitable. What else can you configure "so easily" I wonder?
Then you get into how they are hacking CSS and iframes into the email body, to substitute for Javascript, and actually create a workable user interface. Now this is fascinating, impressive, and deserves further study... Without fully understanding exactly what they are doing, however, it sounds highly abusive of the Mail app's rendering capabilities, and points to exploitable paths within the Mail app that probably need to be tightened up by Apple. If LinkedIn can make an email "act" like that without any opt-in on my part, how would Mallory use the same "feature" in their latest SPAM campaign?
<s>Thanks LinkedIn... really, I'm impressed. When exactly did Walter Bishop start working for you?</s>
P.S. I look forward to following your pending class-action lawsuit for violation of US federal wiretapping laws. Cheers!