Live data from Hacker News

LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

thenextweb.com

21–30 of 43 posts

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#21
Putting aside the issue that much of this data shouldn't have been sent anywhere in the first place, I'll never understand why, in 2012, SSL is still not used by default when sending any sensitive or private data across the network.

It's even more puzzling when we're talking about background data upload when the potential SSL handshake latency isn't going to pose any UX issue. This has boggled my mind for years actually. Why?

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#22
post #10

This is only tangentially related but I really don't understand why anyone cares so highly about their contact list. Does it really matter? Why does it matter? Concerns about spam seem anachronistic (in that you have to deal with spam and services like Gmail have become pretty good at countering it). Is it just privacy? If so, I'm confused.

Will you post your email and cell contacts to this thread now? If not, why not?

I'm confused that you're confused. There are a hundred scenarios I can think of. Gmail being good at spam detection is your defense? For one, I get text message spam all the time now. I dont want people having my number who don't need it.

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#23
post #21

Putting aside the issue that much of this data shouldn't have been sent anywhere in the first place, I'll never understand why, in 2012, SSL is still not used by default when sending any sensitive or private data across the network. It's even more puzzling when we're talking about background data upload when the potential SSL handshake latency isn't going to pose any UX issue. This has boggled my mind for years actua…

Maybe it's not an issue for LinkedIn, but the iOS app submission process requires developers to do a lot of paperwork with several governments (US, France) for export compliance when using any kind of crypto.

I can easily see smaller developers deciding to go for HTTP instead of HTTPS just to avoid dealing with all that bureaucracy.

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#24
post #22
post #10

This is only tangentially related but I really don't understand why anyone cares so highly about their contact list. Does it really matter? Why does it matter? Concerns about spam seem anachronistic (in that you have to deal with spam and services like Gmail have become pretty good at countering it). Is it just privacy? If so, I'm confused.

Will you post your email and cell contacts to this thread now? If not, why not? I'm confused that you're confused. There are a hundred scenarios I can think of. Gmail being good at spam detection is your defense? For one, I get text message spam all the time now. I dont want people having my number who don't need it.

@cletus: would be interesting to see your response to the parent.

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#25
post #23
post #21

Putting aside the issue that much of this data shouldn't have been sent anywhere in the first place, I'll never understand why, in 2012, SSL is still not used by default when sending any sensitive or private data across the network. It's even more puzzling when we're talking about background data upload when the potential SSL handshake latency isn't going to pose any UX issue. This has boggled my mind for years actua…

Maybe it's not an issue for LinkedIn, but the iOS app submission process requires developers to do a lot of paperwork with several governments (US, France) for export compliance when using any kind of crypto. I can easily see smaller developers deciding to go for HTTP instead of HTTPS just to avoid dealing with all that bureaucracy.

I should go back and take a look at the exact wording of the Apple App Store rules but I never had problems submitting apps that use SSL.

There's one step of the submission process that asks about the use of cryptography and I've always picked the option that doesn't require submitting any additional paperwork - never had problems. I forgot the exact wording but I always worked under the assumption that SSL isn't what Apple is talking about when they ask about the use of cryptography.

If developers had to file paperwork with various governments just to use SSL in their app, then simply using one of the many third party APIs that require SSL (e.g. the Foursquare API) or even just embedding a web browser view that may end up loading an https URL would require the developer to go through the paperwork route to get their app approved. That wouldn't make sense.

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#27
post #22
post #10

This is only tangentially related but I really don't understand why anyone cares so highly about their contact list. Does it really matter? Why does it matter? Concerns about spam seem anachronistic (in that you have to deal with spam and services like Gmail have become pretty good at countering it). Is it just privacy? If so, I'm confused.

Will you post your email and cell contacts to this thread now? If not, why not? I'm confused that you're confused. There are a hundred scenarios I can think of. Gmail being good at spam detection is your defense? For one, I get text message spam all the time now. I dont want people having my number who don't need it.

> Will you post your email and cell contacts to this thread now? If not, why not?

Well that is completely different to what LinkedIn is doing.

Sending information via plain text is bad but is fairly unlikely to be read in transit. (This isn't to say that it shouldn't be changed)

LinkedIn shouldn't be collecting the data. At the same time it isn't making the data public. It is somewhat unclear what they are doing with it. It is unlikely though that is for some evil scheme.

Compare this to posting a tonne of personal information on what is essentially a public forum. Completely different.

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#28
post #6

This is off topic, but the next web really needs to make an effort to properly credit images. They've been called out on this a number of times before, but the way they credit image sources is just plain wrong. In this article, for example, at the very bottom of the page is a generic link that says SOURCES: IMAGE CREDIT. With this particular image, the photographer very clearly says "please, kindly credit me (Nan Pal…

And if the photographer is reading - PLEASE FILE A DMCA TAKEDOWN NOTICE.

(Companies aren't going to pay attention to you as a little guy until you kick them in the pants. Have at it.)

Re: LinkedIn’s iOS app transmits names, emails, and calendar notes, in plain text

#29
post #25
post #23

Earlier quoted context omitted.

Maybe it's not an issue for LinkedIn, but the iOS app submission process requires developers to do a lot of paperwork with several governments (US, France) for export compliance when using any kind of crypto. I can easily see smaller developers deciding to go for HTTP instead of HTTPS just to avoid dealing with all that bureaucracy.

I should go back and take a look at the exact wording of the Apple App Store rules but I never had problems submitting apps that use SSL. There's one step of the submission process that asks about the use of cryptography and I've always picked the option that doesn't require submitting any additional paperwork - never had problems. I forgot the exact wording but I always worked under the assumption that SSL isn't wha…

You would think so, but I've never been able to find a definitive answer, in public at least. Some forum posts seem to imply you should answer YES if you utilize HTTPS/SSL even if it's just through the iOS standard frameworks. Whether anyone _really_ cares remains to be seen. The vague wording is probably Apple's way to C.Y.A. should any problems arise later.
Post reply on HN