Return-Path: X-Original-To: mross@acm.jhu.edu Delivered-To: mross@acm.jhu.edu Received: by secure.acm.jhu.edu (Postfix, from userid 91) id 675D0CF009; Wed, 18 Oct 2006 11:12:43 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on centaur.acm.jhu.edu X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,FORGED_RCVD_HELO autolearn=failed version=3.1.4 Received: from jhuin3.jhu.edu (jhuin3.jhu.edu [128.220.2.64]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "smtpint.johnshopkins.edu", Issuer "Equifax" (not verified)) by secure.acm.jhu.edu (Postfix) with ESMTP id 63E5CCEE58 for ; Wed, 18 Oct 2006 11:12:36 -0400 (EDT) Received: from ipex12.johnshopkins.edu (ipex12.johnshopkins.edu [162.129.8.143]) by jhuin3.jhu.edu (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPS id <0J7C00JVX7KYLE20@jhuin3.jhu.edu> for mross@acm.jhu.edu; Wed, 18 Oct 2006 11:12:36 -0400 (EDT) Received: from jhuadig.admin.jhu.edu (HELO ipex1.johnshopkins.edu) ([10.15.69.48]) by ipex12.johnshopkins.edu with ESMTP/TLS/RC4-SHA; Wed, 18 Oct 2006 11:12:30 -0400 Received: from jhuadig.admin.jhu.edu (HELO cis27.hosts.jhmi.edu) ([10.15.69.48]) by ipex1.johnshopkins.edu with ESMTP/TLS/AES256-SHA; Wed, 18 Oct 2006 11:12:30 -0400 Received: from Jhmipri-MTA by cis27.hosts.jhmi.edu with Novell_GroupWise; Wed, 18 Oct 2006 11:12:30 -0400 Date: Wed, 18 Oct 2006 11:12:26 -0400 From: DONALD WINAKER Subject: Re: Inquiry about e-mails which have not been replied to [81111:23473] In-reply-to: To: mross@acm.jhu.edu, dwinaker@jhu.edu Cc: Dean Zarriello , Darren Lacey , Jennifer Peterson Message-id: <45360C1A0200001F0000CAAF@cis27.hosts.jhmi.edu> MIME-version: 1.0 X-Mailer: Novell GroupWise Internet Agent 7.0.1 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-disposition: inline X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AQAAANLhNUUN X-IronPort-AV: i="4.09,325,1157342400"; d="scan'208"; a="7411670:sNHT28591083" X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,325,1157342400"; d="scan'208"; a="82454445:sNHT150441482" References: <44F550EE0200001F00008B35@cis27.hosts.jhmi.edu> Status: O X-UID: 363 Content-Length: 3678 X-Keywords: Michael, there have been a number of conversations with members of my team, the network group, and the Chief Information Security Officer regarding this request. As previously noted, we cannot unblock port 6667 as this increases our security exposure. Unfortunately we also cannot open up all of the sites you requested either. My next suggestions would be to narrow your list to ten or fewer sites and give us the internal addresses that need the access. >>> Michael Ross 10/14/2006 9:19:24 PM >>> I sent you the request for specific addresses as you specified in the e-mail I am replying to on 8/30/06 . It has been over a month and none of the requests have been implemented. What is the ETA for the requests to be implemented? Thanks. Michael Ross on 8/30/06 8:48 AM, DONALD WINAKER at dwinaker@jhu.edu wrote: > Michael, > I believe we offered to enable this for specific addresses that you > request. We cannot enable this for everyone to everything from jhu.edu. > We get hundreds of requests for changes to firewall rules, we are trying > to strike a balance of providing necessary access without developing > processes that are too cumbersome for us to manage. > > Thanks, Don > >>>> Michael Ross 8/29/2006 5:37 PM >>> > Would it be possible to allow outgoing traffic on port 6667 from > *.jhu.edu > but not from *.jhmi.edu? > > I would be happy to discuss this issue further. > > Thanks. > > > on 8/28/06 2:48 PM, network.security at network.security@jhmi.edu > wrote: > >> Please give me a call at 410-735-4337 to discuss this further. >> >> Johns Hopkins Network Security >> Network and Telecommunication Services >> Johns Hopkins University and Medical Institutions >> >>> -----Original Message----- >>> From: "Michael Ross" >>> Received: 8/28/2006 2:03 PM >>> To: "network.security" >>> Subject: Re: Inquiry about e-mails which have not been replied to >>> [81111:23469] >>> >>> Why not just unblock port 6667 for outgoing connections? Since > existing >>> mechanisms (see http://it.jhu.edu/restricted/infosec/blocklist.html > ) >>> automatically detect and block hosts with malware which uses IRC, > clearly, >>> blocking outgoing traffic on port 6667 only blocks legitimate > traffic >>> because hosts sending traffic from malware are already automatically > blocked >>> by the mechanism seen at > http://it.jhu.edu/restricted/infosec/blocklist.html >>> . >>> >>> Keep in mind IRC has many legitimate uses. For example, > irc.freenode.net has >>> many IRC channels (chat rooms) for help with open source software. > It also >>> educational channels (chat rooms) from organizations like NASA. >>> Additionally, irc.mozilla.org has channels (chat rooms) for help > with >>> Firefox. >>> >>> >>> I would be happy to discuss this issue further. >>> >>> Thank you. >>> >>> >>> on 8/28/06 11:33 AM, network.security at network.security@jhmi.edu > wrote: >>> >>>> Is there a specific IRC server you would like access to? >>>> >>>> Johns Hopkins Network Security >>>> Network and Telecommunication Services >>>> Johns Hopkins University and Medical Institutions >>>> >>>>> -----Original Message----- >>>>> From: "Michael Ross" >>>>> Received: 8/27/2006 4:50 PM >>>>> To: network.security@jhu.edu >>>>> Subject: RE: Inquiry about e-mails which have not been replied to >>>>> >>>>> On 7/28/06, I sent an e-mail to network.security@jhu.edu with the > subject >>>>> "Request for port unblocking". I have received a reply. >>>>> >>>>> What is the status? What is going on? Thanks. >>>>> >>>>> Michael Ross >>>>> >>>>> >>> >>>