HDTenEightyP/NetNews huggingface dataset:
From: ckd@eff.org (Christopher Davis)
Subject: Re: Policy regarding Crack
Organization: Electronic Frontier Foundation Tech Central
	<1992Aug26.170825.29391@m.cs.uiuc.edu>
	<1992Aug26.174017.1077@ms.uky.edu>
Date: Thu, 27 Aug 1992 02:17:46 GMT

Wes> == Wes Morgan <morgan@ms.uky.edu> 

 Wes> Seriously, let's look at the possibilities:

 Wes> 	- I can set a simple policy that says "this system is not to be used
 Wes> 	  for the development or use of password cracking software".  My users
 Wes> 	  are Engineering students; they have no curricular need to develop
 Wes> 	  such software on our systems.  

 Wes> 	  This approach benefits everyone (in theory).  The users don't have
 Wes> 	  to worry about admins (or Crack users) rooting through their files, 
 Wes> 	  and I don't have to worry about Crack fanciers.......

Or you could run shadow passwords, and run Crack yourself, and have a
proactive password checker.

This also benefits everyone, because it means that people are less
likely to have their accounts broken into, you don't get into problems
with people being duped into giving out your /etc/passwd for Joe Cracker
to run through Crack on his 486/50 (or on the SS2 he broke into last
week), and even if someone does get your shadow file, your passwords
will have some degree of strength.

I realize that this isn't always doable, but it's a big improvement.

--
Christopher Davis * ckd@eff.org * System Administrator, EFF * +1 617 864 0665
            ``Ed Gruberman, you fail to grasp Ti Kwan Leep.
            Approach me that you might see.'' -- The Master
Newsgroups: comp.admin.policy
From: pbeach@abacus.bates.edu (Preston Beach)
Subject: Should Alums have access to school accounts?
Organization: Bates College, Lewiston, Maine
Date: Wed, 2 Sep 1992 18:52:10 GMT
Originator: pbeach@abacus.bates.edu


At out college, alumni have free access to every school facility but one.
They are currently not allowed to have accounts on our mainframe. I have 
been proposing (for the sake of some alum friends) that that rule be changed
so that LOCAL area alums or alums who are staying in the area can have 
temporary accounts. I consider this to be an ok plan considering that alums
have all the other facilities available. I would like to know what the
policies concerning this are for other colleges and universities. Please
post here or email me. Thanks in advance.
-Preston

EMAIL : pbeach@abacus.bates.edu
Bates College
From: S_TITZ@iravcl.ira.uka.de (Olaf Titz)
Newsgroups: comp.admin.policy
Subject: Re: Policy regarding Crack
Date: 27 Aug 92 12:38:08 GMT
Organization: Fachschaft Informatik, Uni Karlsruhe
X-News-Reader: VMS NEWS 1.23

In <1992Aug26.174017.1077@ms.uky.edu> morgan@ms.uky.edu writes:

>  Seriously, let's look at the possibilities:
>  
>  	- I could (as the admin) sweep through all the user files,
>  	  looking for Crack source/binaries.  This is unacceptable.
>...
>  	- I could write an automated shell script that examines every
>  	  text file on the system, reporting the names of any files which
>  	  are in /etc/passwd format (i.e. Crack food).  This borders on the 
>  	  unacceptable.

It *is* unacceptable, IMHO - the same thing of searching user files.

>  OR.......
>  
>  	- I can set a simple policy that says "this system is not to be used
>  	  for the development or use of password cracking software".  My users
>  	  are Engineering students; they have no curricular need to develop
>  	  such software on our systems.  
>  
>  	  This approach benefits everyone (in theory).  The users don't have
>  	  to worry about admins (or Crack users) rooting through their files, 
>  	  and I don't have to worry about Crack fanciers.......

Are you sure that setting a policy will *prevent* your system from
being Crack'ed? ;;-)

>...
>  Computing resources are usually assigned/allocated within this framework.
>  However, assignments/allocations of these resources for purposes outside
>  of the framework can (and should) be limited.  A Mechanical Engineering 
>  student may wish to write a Japanese text parser; while that is a laudable
>  project, can we justify the allocation of Engineering resources to that
>  goal?  
>  
>  "Academic freedom" is not equivalent to "a blank check".

Right, but... be VERY careful about that.

The step from your Japanese parser to general restrictions like 'we
don't carry alt* and rec* newsgroups' is dangerously short. Take
another example: When I want books from my university library, nobody
cares about the importance of, say, a book on music history for my
computer science studies. Not a blank check, but the provision of
CERTAIN resources for own use (as opposed to the provision of
resources for CERTAIN use - understood?)

I don't know about your engineering department, and I know that this
is a heatedly debated issue since computers exist (are games allowed?
and so on) but I think universities should provide the resources they
are able to (technically, financially,...) and place no restrictions
on their use unless there are justifiable reasons to do so, e.g.
outright abuse (what this is, however, should not be stated par ordre
du mufti but established, ideally, by a board of staff AND students).

MfG,
        Olaf
-- 
Olaf Titz - comp.sc.student - Univ of Karlsruhe - s_titz@iravcl.ira.uka.de -
uknf@dkauni2.bitnet - praetorius@irc - +49-721-60439 - did i forget something?
One frequently hears horror expressed that a 2M byte machine may have 400K
 devoted to its operating system. - Fred Brooks (1975)
Newsgroups: comp.admin.policy,alt.comp.acad-freedom.talk
From: bob@romeo.caltech.edu (Robert S. Logan)
Subject: Re: Should Alums have access to school accounts?
Organization: California Institute of Technology, Pasadena
Date: Thu, 3 Sep 1992 00:15:10 GMT

In article <1992Sep2.185210.17665@orlith.bates.edu>, pbeach@abacus.bates.edu (Preston Beach) writes...
>
>At out college, alumni have free access to every school facility but one.
>They are currently not allowed to have accounts on our mainframe. I have
>been proposing (for the sake of some alum friends) that that rule be changed
>so that LOCAL area alums or alums who are staying in the area can have
>temporary accounts. I consider this to be an ok plan considering that alums
>have all the other facilities available. I would like to know what the
>policies concerning this are for other colleges and universities. Please
>post here or email me. Thanks in advance.
>-Preston
>
>EMAIL : pbeach@abacus.bates.edu
>Bates College

At Caltech, our Alumni Association bought a SPARCstation and gives any member
an account. It is in the same group of Suns and NeXTs that students use, so
they feel right at home (recent grads anyway). This makes it nicer for us
(we run that cluster) since when a graduating student wants to keep an account,
we just say 'join the Alumni Association'. It is also a good incentive for
recent grads to join the association. So everyone is happy.

Bob Logan
bob@cco.caltech.edu
From: jaw@owlnet.rice.edu (Joseph A. Watters)
Newsgroups: comp.admin.policy
Subject: Re: Policy regarding Crack
Date: 26 Aug 1992 21:19:34 GMT
Organization: Rice University

In article <mumble>, dan@cubmol.bio.columbia.edu (Daniel Zabetakis) writes:
|> 
|>     Does anyone have in thier usage policy mention of Crack, or COPS,
|> or other programs that could be used for unnacceptable purposes?
|>     Does anyone not allow possesion of Crack? How about running it?

At Rice, we do not explicitly disallow the possession or running of
either of these programs.  If we caught someone using them for
unacceptable purposes, we could take action against them for trying to
break in to systems that they are not authorized to use.  Our policies
prohibit unacceptable actions, regardless of the mechanism or
technology used to perform them.  For some systems here, our defense is
to run them ourselves regularly, and strongly encourage/force users
whose accounts are vulnerable according to these programs to close the
vulnerabilities.  In the case of crack, if it guesses a password, we
have the user change to an unguessable (by crack) password.  We use
COPS regularly to audit for its list of security holes, such as world
readable/writable .rhosts files, and have the users close those too.

There are many different groups managing computers here on campus, and
not all of them use these methods, to my knowledge.  The systems that
do use these methods comprise the largest networks on campus, with by
far the largest number of users.  The good thing about using COPS is
that it protects the networks that use it from some of the weaknesses
of the other networks on campus.

-- 
Joseph A. Watters, Jr.		jaw@owlnet.rice.edu
Deputy Director, Owlnet
Rice University
Houston, Texas
Newsgroups: comp.admin.policy,comp.unix.admin
From: hogan@boetius (Kharim Hogan)
Subject: Commercial companies on the internet via a university -- RFC??
Organization: Los Alamos National Laboratory, NM
Date: Thu, 27 Aug 92 02:20:42 GMT

Hi,

Does anybody know if an RFC exists concerning and/or dealing with the issue
of commercial companies wnating and/or getting accounts on university based
networks.  i.e. what are the policies regarding a commercial company with
a 'university.edu' email address?  Is this legal?  I was under the impression
that such companies had to acquire their own '.com' type access to the
internet.

If anyone can point me to information on this (RFC or otherwise), I would
be very grateful.

Thanks,

Kharim Hogan
System Administrator, Faculty of Music, McGill University


-- 
********************************
       Kharim M. Hogan
     hogan@music.mcgill.ca
********************************
Newsgroups: comp.admin.policy,alt.comp.acad-freedom.talk
From: ckd@eff.org (Christopher Davis)
Subject: Re: Policy regarding Crack
Organization: Electronic Frontier Foundation Tech Central
	<CKD.92Aug26221743@loiosh.eff.org> <1992Aug27.115813.28741@ms.uky.edu>
Date: Thu, 27 Aug 1992 23:29:10 GMT

Wes> == Wes Morgan <morgan@ms.uky.edu> 

First, I think we're in violent agreement, just talking past each other
a bit.  My main point was that preventing Crack use on your systems
doesn't stop the Evil Ones from taking your file elsewhere (not
something I think you'd argue against ;-) and that to protect *your*
systems, the only real method is to protect your passwords through
proactive (npasswd, etc), reactive (Crack), and preventative (shadow)
methods.

 Wes> Why, then, should our assistance be restricted to reactive
 Wes> functions?  If I can take steps to prevent potential problems
 Wes> WITHOUT affecting my core mission (Engineering education, in my
 Wes> case), why *shouldn't* I do so?

No reason at all.

 Wes> I believe that I, as a sysadmin, have a certain obligation to the
 Wes> other systems using our common network(s).  Why should I allow my
 Wes> system to be used as a 'forward base' from which to attack other
 Wes> systems?  Should I adopt an attitude such as "well, he's not
 Wes> cracking MY password file, so I don't care"?  If I found someone
 Wes> attempting to crack the password file for kragar.eff.org, wouldn't
 Wes> you want me to notify you?  If so, why shouldn't I prevent it in
 Wes> the first place, if such a goal is (relatively) attaniable?

I agree that preventing this behavior is important, just that it's not
sufficient.  One of the rules on our systems is that using them to
attack other systems is prohibited, and certainly I'd notify you if I
found someone cracking your password file, as much as I'd like you to
notify me if someone were cracking one of mine.

Again, however, if they take it off to their quiet corner of the
computing world to crack it, neither of us will ever know, so it
behooves us to take advantage of various protective methods...

(Hopefully this thread will give some of the novice system
administrators you referred to in the sections I deleted a chance to
learn more about what they can do to protect their machines.)
--
Christopher Davis * ckd@eff.org * System Administrator, EFF * +1 617 864 0665
            ``Ed Gruberman, you fail to grasp Ti Kwan Leep.
            Approach me that you might see.'' -- The Master
From: ehunt@bsc835bsc.edu (Eric Hunt)
Newsgroups: comp.admin.policy
Subject: Re: Should Alums have access to school accounts?
Date: 3 Sep 92 21:15:22 GMT
Organization: Birmingham-Southern College

In article <1992Sep2.185210.17665@orlith.bates.edu>, pbeach@abacus.bates.edu (Preston Beach) writes:
> policies concerning this are for other colleges and universities. Please

Here at 'Southern, it's my understanding that alums are allowed to keep their
HP-9000 accounts. I think our director of Academic Computing reads this group,
he might chime in with a relevant bit or two.
-- 
Eric Hunt                     | bsc835!ehunt@uunet.uu.net (preferred)
Birmingham-Southern College   | eric.hunt@matrix.sbs.com
Birmingham, Alabama 35254     |          ^----nothing longer than 100 lines
Newsgroups: comp.admin.policy,alt.comp.acad-freedom.talk
From: lfoard@Turing.ORG (Lawrence C. Foard)
Subject: Re: Policy regarding Crack
Organization: The Turing Project, Charlottesville Virginia.
Date: Fri, 28 Aug 1992 02:29:23 GMT

Or you could run crack yourself and fix the holes...

-- 
>>Unix/C Contract worker available 5 years C/unix work experience<<  ______
Available for Telecommuting/Travel and contracts on the T Line       \    /
in the Boston MA area. Send me e-mail for a copy of my Resume.        \  /
       -- VWIS 508-793-9568 (2400 baud), Linux support BBS.--          \/
Newsgroups: comp.admin.policy
From: cavrak@emba-news.uvm.edu.UUCP (Steve Cavrak)
Subject: Re: Should Alums have access to school accounts?
Originator: cavrak@newton.emba.uvm.edu
Organization: University of Vermont -- Division of EMBA Computer Facility
Date: Thu, 3 Sep 1992 01:46:15 GMT

I believe that one University in Colorado - Colorado State University?,
University of Colorado at Fort Collins? - has a "lifetime" account.

There, from what I gather, education, and hence computing, are seen as
life long ventures, and they would like to have their alumni keep 
coming back.  Sure, maybe only 1% uses the resource -- but 1% would
be an excellent response rate for alumni.  If it were 10%, that
would be astounding!  And a major coup.

Ciao
Steve
Newsgroups: comp.admin.policy,comp.unix.admin
From: john@iastate.edu (John Hascall)
Subject: Re: Commercial companies on the internet via a university -- RFC??
Organization: Iowa State University, Ames, IA
Date: Fri, 28 Aug 1992 02:09:30 GMT

hogan@boetius (Kharim Hogan) writes:

}Does anybody know if an RFC exists concerning and/or dealing with the issue
}of commercial companies wnating and/or getting accounts on university based
}networks.  i.e. what are the policies regarding a commercial company with
}a 'university.edu' email address?  Is this legal?  I was under the impression
}that such companies had to acquire their own '.com' type access to the
}internet.

I dunno about the rules, but a company in ISU's research park has a
xxx.iastate.edu address (which I am against, but nobody asked me).

John
-- 
John Hascall                                       ``Live with it pink-boy!''
Project Vincent                                                              
Iowa State University Computation Center                     john@iastate.edu
Ames, IA  50011                                      515/294-9551 [fax -1717]
Newsgroups: comp.admin.policy
From: gary@resumix.portal.com (Gary Lin)
Subject: Alumni access privileges
Summary: Charging graduates for access
Organization: Resumix Inc.
Date: Thu, 3 Sep 92 15:50:20 GMT


UC Santa Cruz offers members of the Alumni Assoc. so-called "sundry" accounts
where for yearly fee of $45 a regular computer account.  Your account is
treated like all other student/staff users except for billing purposes.
The only other fee is if you want to print (to pay for paper).

Then again, I imagine quite a few schools also where people can get accounts
simply because they know the computer center staff.

						Gary M. Lin
						gary@resumix.portal.com
Newsgroups: comp.admin.policy
From: dan@cubmol.bio.columbia.edu (Daniel Zabetakis)
Subject: Policy regarding Crack
Organization: Columbia University, Dept. of Biological Sciences.
Date: Wed, 26 Aug 1992 15:08:55 GMT


    Does anyone have in thier usage policy mention of Crack, or COPS,
or other programs that could be used for unnacceptable purposes?
    Does anyone not allow possesion of Crack? How about running it?

DanZ

-- 
This article is for entertainment purposes only. Any facts, opinions,
narratives or ideas contained herein are not necessarily true, and do
not necessarily represent the views of any particular person.  

Newsgroups: comp.admin.policy,alt.comp.acad-freedom.talk
From: mjo@ef2007.efhd.ford.com (Mike O'Connor)
Subject: Re: Should Alums have access to school accounts?
X-Disclaimer: Not an official spokesperson for Ford OPEO
Reply-To: Mike O'Connor <mjo@fmsrl7.srl.ford.com>
Organization: International Affairs, Overseas Engineering, "Fordz"
Date: Thu, 3 Sep 1992 21:54:45 GMT

In article <1992Sep3.172802.6586@ms.uky.edu> morgan@ms.uky.edu (Wes
Morgan) writes:

:I *might* be concerned about alumni using university resources for corporate
:purposes.  
:
:Some vendors stipulate 'educational use only' when they donate equipment
:and/or software.  If alumni start doing research for their employers on
:university equipment, you might run into some problems.....
:
:I would think that a simple 'no commercial use' agreement with the alumnus
:would eliminate such problems......

It strikes me that the alums should follow the same computing use
policy as the students, and that a "no commercial use" policy would
apply equally to students and alumni.


					...Mike

-- 
 Michael J. O'Connor           |  Internet:  mjo@fmsrl7.srl.ford.com
 Ford Motor Company, OPEO      |  UUCP:      ...!{backbone}!fmsrl7!mjo
 20000 Rotunda, Bldg. 1-3001   |  Phone:     +1 (313) 248-1260
 Dearborn, MI  48121           |  Fax:       +1 (313) 323-6277
Newsgroups: comp.admin.policy
Subject: Staffing needs of handicapped access lab
From: ssaltz@cabell.vcu.edu (Steven A. Saltzberg)
Date: Fri, 28 Aug 1992 12:22:19 GMT
Expires: Wed, 30 Sep 1992 04:00:00 GMT
Organization: Virginia Commonwealth University
Keywords: handicapped computer staff
Summary: Need information on staffing needs of lab for handicapped


We have been funded to install two workstations for the handicapped
(wheelchair access, hearing and visually impaired, etc).  And have
no idea what the staffing requirements might be.  If any of you have
experience here, please respond in this group or via email at

ssaltz@cabell.vcu.edu

Thanks,

steve saltzberg
academic campus computing services
virginia commonwealth university
richmond virginia
Newsgroups: comp.admin.policy
From: morgan@ms.uky.edu (Wes Morgan)
Subject: Re: Should Alums have access to school accounts?
Date: Thu, 3 Sep 1992 21:28:02 GMT
Organization: The Puzzle Palace, UKentucky

pbeach@abacus.bates.edu (Preston Beach) writes:
>
>At out college, alumni have free access to every school facility but one.
>They are currently not allowed to have accounts on our mainframe. I have 
>been proposing (for the sake of some alum friends) that that rule be changed
>so that LOCAL area alums or alums who are staying in the area can have 
>temporary accounts. I consider this to be an ok plan considering that alums
>have all the other facilities available. 

I *might* be concerned about alumni using university resources for corporate
purposes.  

Some vendors stipulate 'educational use only' when they donate equipment
and/or software.  If alumni start doing research for their employers on
university equipment, you might run into some problems.....

I would think that a simple 'no commercial use' agreement with the alumnus
would eliminate such problems......

--Wes

-- 
MORGAN@UKCC         |       Wes Morgan       |        ...!ukma!ukecc!morgan 
morgan@ms.uky.edu   | Engineering  Computing |   morgan@wuarchive.wustl.edu
morgan@engr.uky.edu | University of Kentucky | JWMorgan@dockmaster.ncsc.mil
  Mailing list for AT&T StarServer S/E  - starserver-request@engr.uky.edu
Newsgroups: comp.admin.policy
From: john@iastate.edu (John Hascall)
Subject: Re: Should Alums have access to school accounts?
Organization: Iowa State University, Ames, IA
Date: Fri, 4 Sep 1992 02:44:11 GMT

pbeach@abacus.bates.edu (Preston Beach) writes:
}At out college, alumni have free access to every school facility but one.
}They are currently not allowed to have accounts on our mainframe. I have 
}been proposing (for the sake of some alum friends) that that rule be changed
}so that LOCAL area alums or alums who are staying in the area can have 
}temporary accounts. I consider this to be an ok plan considering that alums
}have all the other facilities available. I would like to know what the
}policies concerning this are for other colleges and universities. Please
}post here or email me. Thanks in advance.

We do not currently allow alumni to keep their accounts after they leave
(other than it is a year after graduation that we `figure out' that they
are gone).  I have been pushing to allow alumni to keep their accounts
without luck so far, but now I have an unexpected ally -- the Engineering
College Placement Office has moved their services onto our system -- and
they offer their services to graduates for life...   :-)

John
-- 
John Hascall                                       ``Live with it pink-boy!''
Project Vincent                                                              
Iowa State University Computation Center                     john@iastate.edu
Ames, IA  50011                                      515/294-9551 [fax -1717]
Newsgroups: comp.admin.policy
From: dmjones@THEORY.LCS.MIT.EDU ("David M. Jones")
Newsgroups: comp.archives
Subject: [comp.theory] Online LICS bibliography
Followup-To: comp.theory
Date: 2 Sep 1992 04:34:42 GMT
Organization: University of California, Berkeley
Distribution: world
Reply-To: Theory-A - TheoryNet World-Wide Events <THEORY-A%NDSUVM1.BITNET@cmsa.Berkeley.EDU>,
NNTP-Posting-Host: soda.berkeley.edu
X-Original-Newsgroups: comp.theory
X-Original-Date: 1 Sep 92 01:01:16 GMT

Archive-name: auto/comp.theory/Online-LICS-bibliography

The online bibliography for the Annual IEEE Symposium on Logic in Computer
Science has now been updated to include all of the papers published in the
proceedings of the Seventh meeting, which took place in June 1992.  The
bibliography contains abstracts for all of the papers from the 1992
meeting.

The bibliography, which is in BibTeX format, is available via anonymous ftp
and mail server from theory.lcs.mit.edu [18.52.0.92] in the file
pub/meyer/lics.bib.

To retrieve the file via ftp, connect to theory using "anonymous" as the
login name and "guest" as the password.

To retrieve the file via mail server, send a message to the address
archive-server@theory.lcs.mit.edu with the following line in the body:

        send meyer lics.bib

An index of other available files can be retrieved with the command

        send meyer Index

More information on the archive-server can be obtained by sending a message
with only the word "help" in the body.

David M. Jones
MIT Lab for Computer Science
Administrator, {types,logic,concurrency}@theory.lcs.mit.edu