[From nobody Tue Feb 16 08:33:54 2010 Return-Path: <purdue-pm-bounces+djacoby=purdue.edu@pm.org> Received: via tmail-2007e.22 (invoked by user mailnull) for djacoby; Tue, 16 Feb 2010 11:27:58 -0500 (EST) Return-Path: <purdue-pm-bounces+djacoby=purdue.edu@pm.org> Received: from mailhub180.itcs.purdue.edu (mailhub180.itcs.purdue.edu [128.210.5.180]) by mailhub051.itcs.purdue.edu (8.14.3/8.14.3/store-smtp) with ESMTP id o1GGRwbq000870 for <djacoby@purdue.edu>; Tue, 16 Feb 2010 11:27:58 -0500 Received: from mailhub248.itcs.purdue.edu (mailhub248.itcs.purdue.edu [128.210.5.248]) by mailhub180.itcs.purdue.edu (8.14.2/8.14.2/spamscan) with ESMTP id o1GGRwH0008894 for <djacoby@purdue.edu>; Tue, 16 Feb 2010 11:27:58 -0500 Received: from x6.develooper.com (x6.develooper.com [207.171.7.86]) by mailhub248.itcs.purdue.edu (8.14.2/8.14.2/smtp.purdue.edu) with ESMTP id o1GGRvHE007888 for <djacoby@purdue.edu>; Tue, 16 Feb 2010 11:27:57 -0500 Received: from x6.develooper.com (localhost.localdomain [127.0.0.1]) by x6.develooper.com (Postfix) with ESMTP id A20A917742 for <djacoby@purdue.edu>; Tue, 16 Feb 2010 08:27:56 -0800 (PST) Subject: Re: [Purdue-pm] Conflict with WIFi security From: purdue-pm-owner@pm.org To: djacoby@purdue.edu MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1445657799==" Message-ID: <mailman.1633.1266337675.2577.purdue-pm@pm.org> Date: Tue, 16 Feb 2010 08:27:55 -0800 Precedence: bulk X-BeenThere: purdue-pm@pm.org X-Mailman-Version: 2.1.11 List-Id: Purdue Perl Mongers mailing list <purdue-pm.pm.org> X-List-Administrivia: yes Sender: purdue-pm-bounces+djacoby=purdue.edu@pm.org Errors-To: purdue-pm-bounces+djacoby=purdue.edu@pm.org X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.2.16.161538 X-PMX-Version: 5.5.7.378829 X-PerlMx-Virus-Scanned: Yes X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, NO_REAL_NAME 0, TO_NO_NAME 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 0, __HAS_MSGID 0, __MIME_VERSION 0, __RFC822_ATTACH 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NS ' --===============1445657799== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at purdue-pm-owner@pm.org. --===============1445657799== Content-Type: message/rfc822 MIME-Version: 1.0 Return-Path: <djacoby@purdue.edu> Delivered-To: mailman-purdue-pm@mailman.pm.dev Received: (qmail 24295 invoked from network); 16 Feb 2010 16:27:54 -0000 Received: from x1.develooper.com (207.171.7.70) by x6.develooper.com with SMTP; 16 Feb 2010 16:27:54 -0000 Received: (qmail 364 invoked by uid 225); 16 Feb 2010 16:27:54 -0000 Delivered-To: purdue-pm@pm.org Received: (qmail 356 invoked by uid 103); 16 Feb 2010 16:27:53 -0000 Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 16 Feb 2010 16:27:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=0.0 required=8.0 tests= X-Spam-Check-By: 16.mx.develooper.com Received: from mailhub131.itcs.purdue.edu (HELO mailhub131.itcs.purdue.edu) (128.210.5.131) by 16.mx.develooper.com (qpsmtpd/0.80) with ESMTP; Tue, 16 Feb 2010 08:27:17 -0800 Received: from mailhub218.itcs.purdue.edu (mailhub218.itcs.purdue.edu [128.210.5.218]) by mailhub131.itcs.purdue.edu (8.14.2/8.14.2/smtp-nopmx) with ESMTP id o1GGR63A024447; Tue, 16 Feb 2010 11:27:06 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhub218.itcs.purdue.edu (8.14.3/8.14.3/webmail-httpd) with ESMTP id o1GGR6gZ015539; Tue, 16 Feb 2010 11:27:06 -0500 Received: from pal-161-222.itap.purdue.edu (pal-161-222.itap.purdue.edu [128.211.161.222]) by boilermail.purdue.edu (Horde Framework) with HTTP; Tue, 16 Feb 2010 11:27:06 -0500 Message-ID: <20100216112706.56220lomrp6j6nhc@boilermail.purdue.edu> Date: Tue, 16 Feb 2010 11:27:06 -0500 From: djacoby@purdue.edu To: Rick Westerman <westerman@purdue.edu> Cc: Purdue Perl Mongers <purdue-pm@pm.org> Subject: Re: [Purdue-pm] Conflict with WIFi security References: <69F91249-D2BE-4E62-B929-52E5D0C5618B@purdue.edu> In-Reply-To: <69F91249-D2BE-4E62-B929-52E5D0C5618B@purdue.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.5) X-PMX-Version: 5.5.7.378829 X-PerlMx-Virus-Scanned: Yes There seems to be another conflict, in that there's a group in the conference room right now. It might be a fight to get the room, and seeing how they're all in Army camo, it's a fight we'd likely lose. Scratch until next week? Quoting Rick Westerman <westerman@purdue.edu>: > Of course Perl doesn't have much to do with WiFi security ... but > our meeting Tomorrow (Feb. 16th) has a conflict with the following. > So we might expect a few less people. Or maybe since the WIFi > talk continues after 1:00 post-lunch (and probably really does not > start until then) people who are interested in it can come to PM > and then leave for WiFi. > > ------------- > > Just a reminder that we have Bob Morrow coming tomorrow to talk > about Wi-Fi Security from > noon to 2:30. > > Wi-Fi (IEEE 802.11) is by far the most common wireless computer > network, and the relentless > tide of sophisticated attacks make security of this system > critically important. Dr Bob Morrow will address > several Wi-Fi security threats, including disclosure, data > integrity, and denial-of-service attacks that can > bring a network to its knees. Simple propagation analysis can > determine a target network's vulnerability to > eavesdropping and jamming. The weaknesses of wired equivalent > privacy (WEP) are legendary, and Bob > will discuss how these are addressed through the IEEE 802.11i > standard with improved authentication, > key distribution, and encryption. methods. Finally, he will provide > a summary of simple ways that wireless > security can be improved beyond simply implementing 802.11i. > > Come bring a lunch, here what this expert in security has to share. It will > be held in STEWART 310. > > ---------- > > -- Rick > > --===============1445657799==-- ]