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...
prev parent reply other threads:[~2012-05-18 0:12 UTC|newest]
Thread overview: 2+ 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]
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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox