On Fri, Oct 25, 2013 at 6:43 PM, Chris Hartley hartl...@gmail.com wrote:
Anyone who has access to logs for their email infrastructure ought
probably to check for authentications to user accounts from linkedin's
servers.
[snip]
Perhaps a prudent countermeasure would be to redirect all POP,
Well said
--
Jason Hellenthal
Voice: 95.30.17.6/616
JJH48-ARIN
On Oct 26, 2013, at 2:06, Jimmy Hess mysi...@gmail.com wrote:
On Fri, Oct 25, 2013 at 6:43 PM, Chris Hartley hartl...@gmail.com wrote:
Anyone who has access to logs for their email infrastructure ought
probably to check for
When a user signs up for a social media account they generally do so by
providing an email address like vic...@freewebmailsite.com and selecting a
password. The social media site can obviously probe freewebmailsite.com and
attempt to authenticate using the same password that you just provided
There's a reason I use an email alias if I sign up to places like
that and why I do not place much information on these sites...
There's a reason I maintain somewhere approaching 20 passwords in my
head too and why the password I use for accessing my own systems will
never be the password I use
(My apologies to those of you who are also on the mailop list and
have already seen these remarks.)
This isn't particularly surprising: LinkedIn are spammers. Have been
since forever. They hit real addresses, fake addresses, mailing lists,
spamtraps, never-existed addresses, everything.
And
I had to answer the question of Why is LinkedIn asking for my GMail
account information to one of my parents recently. Oh it is so they
can access your information and use it It is how some random guys
I play tennis with in a league keep popping up as people I should add,
since they likely
Chris Hartley wrote:
Anyone who has access to logs for their email infrastructure ought
probably to check for authentications to user accounts from linkedin's
servers. Likely, people in your organization are entering their
credentials into linkedin to add to their contact list. Is it a
problem
The other difference is that Google tells you up front, LinkedIn
installed this out of the bleue without any real permissions. Of course
if this where an opt in thing, nobody would be opting in! Well, I never
did install their app and most certainly never will, and am telling all
of my friends
On Sat, Oct 26, 2013 at 7:46 PM, Gary Baribault g...@baribault.net wrote:
The other difference is that Google tells you up front, LinkedIn
installed this out of the bleue without any real permissions. Of course
if this where an opt in thing, nobody would be opting in! Well, I never
did
Scott Howard wrote:
Have you actually confirmed it's NOT opt-in? The screenshots on the
Linked-in engineering blog referenced earlier certainly make it look like
it is.
http://engineering.linkedin.com/sites/default/files/intro_installer_0.png
Of course, you could argue there's a difference
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
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
12 matches
Mail list logo
