IETF Logo Mail Archive

Re: end user security

Austin Bill-P23393 <Bill.Austin@MOTOROLA.COM> Wed, 10 October 2001 16:28 UTC

Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13679 for <run-archive@LISTS.IETF.ORG>; Wed, 10 Oct 2001 12:28:52 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72]) by mailbag.cps.intel.com (8.9.3/8.9.3/d: relay.m4,v 1.6 2000/11/24 22:10:56 iwep Exp iwep $) with ESMTP id JAA28660; Wed, 10 Oct 2001 09:14:35 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 14841 for IETF-RUN@MAILBAG.INTEL.COM; Wed, 10 Oct 2001 09:14:35 -0700
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by mailbag.cps.intel.com (8.9.3/8.9.3/d: relay.m4,v 1.6 2000/11/24 22:10:56 iwep Exp iwep $) with ESMTP id JAA28656 for <IETF-RUN@mailbag.cps.INTEL.COM>; Wed, 10 Oct 2001 09:14:34 -0700 (PDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id JAA04540 for <IETF-RUN@mailbag.cps.INTEL.COM>; Wed, 10 Oct 2001 09:12:30 -0700 (MST)]
Received: [from az33exb01.corp.mot.com (az33exb01.corp.mot.com [199.2.84.12]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id JAA01841 for <IETF-RUN@mailbag.cps.INTEL.COM>; Wed, 10 Oct 2001 09:12:30 -0700 (MST)]
Received: by az33exb01.corp.mot.com with Internet Mail Service (5.5.2654.52) id <42YN70JQ>; Wed, 10 Oct 2001 09:12:30 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <1D74B9231259D511B1AA0002B32C2896410623@az10exm06.sat.mot.com>
Date: Wed, 10 Oct 2001 09:12:20 -0700
Reply-To: IETF-RUN <IETF-RUN@mailbag.cps.INTEL.COM>
Sender: IETF-RUN <IETF-RUN@mailbag.cps.INTEL.COM>
From: Austin Bill-P23393 <Bill.Austin@MOTOROLA.COM>
Subject: Re: end user security
To: IETF-RUN@mailbag.cps.INTEL.COM

In almost all cases, it is not the computer systems that are the problem.  It is almost always "operator error."

The people who will always open that attachment that says "Readme.exe" or "Picture.exe" or "remove.exe" or "resume.doc.pif" are the ones who cause the problems.  There will always be a new exploit, a new worm or virus, a new fraud, urban legend, scam or chain letter.  Systems will never be secure against the brand new, just discovered exploit.  If we write this document, it will probably be a compilation of ancient history that many people have been trying to get people to read for years.  Why do we think they will read it now?

Some source material I have gathered over the years is available here:

http://www.stockhelp.net/virus.html  and the group below is the largest mailing list in the Viruses Category on Yahoo Groups.

http://groups.yahoo.com/group/virushoaxbusters/



Bill Austin, CDMA Systems Division
Motorola Global Telecom Solutions Sector
http://www.motorola.com/aspira/CDMA.htm


-----Original Message-----
From: Bryan Follins [mailto:asalh@MINDSPRING.COM]
Sent: Tuesday, October 09, 2001 10:39 PM
To: IETF-RUN@mailbag.cps.INTEL.COM
Subject: Re: end user security


Check out the documents on my website at www.readingwhitepapers.com
They may help.

Bryan

-----Original Message-----
From: IETF-RUN [mailto:IETF-RUN@MAILBAG.INTEL.COM]On Behalf Of Josh Rollyson
Sent: Tuesday, October 09, 2001 6:56 PM
To: IETF-RUN@MAILBAG.INTEL.COM
Subject: end user security

I'd like to suggest that a document is needed on the responsibilities
of end users to maintain secure systems.

Every day I deal with abuse from compromised systems on broadband
connections. The providers are usually too overwhelmed to take any action,
and the users were usually never informed of the risks, or of their
responsibility to insure their system isn't misused.

v2.23.0 | Report a Bug | By Email