Re: If you're on LinkedIn, and you use a smart phone...

[Phil Bedard <bedard.phil () gmail com>]

I don't see that happening.  I have heard of a couple companies sending out emails saying installing it violates 
company IT policies and I'm sure those using MDM will create policies to disable it.  

It's one of those things which should probably just fade into history quietly.   Maybe LinkedIn should petition Apple 
to find a way to integrate the info.  Windows Phone for instance already internally does exactly what Intro does 
without scraping emails.  

Phil

> On Oct 26, 2013, at 6:20 PM, Andre Tomt <andre-nanog () tomt net> wrote:
>
> > On 26. okt. 2013 08:06, Jimmy Hess wrote:
> > Perhaps a prudent countermeasure would be to redirect all  POP,  IMAP,  and
> > Webmail access to your corporate mail server from all of  LinkedIn's  IP
> > space to a  "Honeypot"   that will simply  log   usernames/credentials
> > attempted.
> >
> > The list of valid credentials,  can then be used to  dispatch a warning to
> > the offender,  and force a password change.
> >
> > This could be a useful proactive countermeasure against the  UIT
> >  (Unintentional Insider Threat);  of employees  inappropriately   entering
> >   corporate  e-mail credentials  into a known  third party service  with
> >  outside of organizational control.
> >
> > Seeing as  Linkedin  almost certainly is not providing signed NDAs and
> >  privacy SLAs;   it seems reasonable that  most organizations who
> > understand what is going on,  would not approve  of use of the service with
> > their internal business email accounts.
>
> Depends on linkedin beeing nice, but could this be an idea? In addition to the proposed network level controls of 
> course. At least users could get a informative response rather than just some dumb error / "it doesnt work" if you 
> block Intro.
>
> http://feedback.intro.linkedin.com/forums/227301-linkedin-intro-feedback/suggestions/4801236-some-way-to-block-intro-per-domain
>
> Votes maybe?
>
> I considered proposing making it opt-in on the domain level, but that wont fly for them I'm sure.