From: Alexander Viro <aviro@redhat.com>
To: Aaron Lippold <lippold@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Invitation to connect on LinkedIn
Date: Thu, 17 May 2012 20:12:48 -0400 [thread overview]
Message-ID: <20120518001248.GA21523@shell.devel.redhat.com> (raw)
In-Reply-To: <773256548.2042913.1337287434330.JavaMail.app@ela4-app0132.prod>
On Thu, May 17, 2012 at 08:43:54PM +0000, Aaron Lippold wrote:
> LinkedIn
> ------------
>
>
>
> I'd like to add you to my professional network on LinkedIn.
>
> - Aaron
>
> Aaron Lippold
> Computer Scientist and Senior Technology Advisor at DISA
> Washington D.C. Metro Area
>
> Confirm that you know Aaron Lippold:
> https://www.linkedin.com/e/69obwb-h2caes7q-6s/isd/7140513257/pdS5zYZx/?hs=false&tok=3OqLvslGLX5Bg1
... and that, gentlemen, is a lovely demonstration of the reasons why
linkedin should be treated as security hazard. I'm fairly sure that
what has happened is that the damn thing had crawled through address
book and spammed everything found there, maillist or no maillist. IOW,
about par for course for malware from a spamhaus, may it go chapter 7...
next prev parent reply other threads:[~2012-05-18 0:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 20:43 Invitation to connect on LinkedIn Aaron Lippold
2012-05-18 0:12 ` Alexander Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 16:59 R Keith Beal (N1ZT)
2014-05-11 18:46 Giri babu
2013-04-27 10:38 Ashish Anand via LinkedIn
2013-04-23 10:59 Vivek P.
2013-04-23 12:07 ` Greg Freemyer
2013-04-20 10:44 Barry Song via LinkedIn
2013-04-16 19:56 Kumar Sukhani via LinkedIn
2013-04-16 20:14 ` rush
2013-04-17 5:15 ` Leon Romanovsky
2013-03-17 10:33 Ashish Anand via LinkedIn
2013-03-01 7:33 Desheng Li via LinkedIn
2013-01-12 3:47 Purandhar Sairam Mannidi
2012-12-11 14:56 dai erxin
2012-12-10 15:31 Guanjun He via LinkedIn
2012-10-15 12:29 Hao Song via LinkedIn
2012-10-10 19:37 Amirali Shambayati via LinkedIn
2012-09-13 9:14 Vitaly Chernooky via LinkedIn
2012-09-10 17:04 harsha priya gupta via LinkedIn
2012-07-11 5:39 Prashant Patil via LinkedIn
2012-05-09 10:11 Anthony Cunningham
2012-04-17 1:16 王劲男 James Wang
2012-03-24 19:31 Kunjan Shah
2012-03-09 8:21 Richard Zhao via LinkedIn
2012-02-28 18:05 Carter Cheng via LinkedIn
2012-01-10 13:28 Bhanu Prakash Singh via LinkedIn
2011-11-27 5:13 Venkateswarlu P via LinkedIn
2011-09-29 8:05 Ajeeshrao r
2011-09-12 17:03 Venugopal Rao via LinkedIn
2011-09-08 3:34 Anil Unnikrishnan via LinkedIn
2011-08-30 6:30 Kuldeep Ghan
2011-08-30 6:30 Kuldeep Ghan
2011-08-22 10:08 Bin Zhao
2011-07-01 9:43 Sugnan prabhu
2011-06-23 4:16 kuberasamrat Vankadari
2011-06-07 6:12 Hong Li
2011-06-04 10:55 david kelman
2011-03-16 14:01 志龙 张
2009-10-29 17:27 Tsavatapalli Ganesh Kumar
2008-11-19 7:10 Arun KS
2008-11-19 7:18 ` Arun KS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120518001248.GA21523@shell.devel.redhat.com \
--to=aviro@redhat.com \
--cc=linux-audit@redhat.com \
--cc=lippold@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.