[Smaug] Zero tolerance for P2P?

John Callaway john.callaway at visicomp.com
Sat, 11 May 2002 20:49:38 -0700

Hash: SHA1

   In addition to shutting down all networking, internal and external, they 
will have to also remove all CD burners (of which there is at least one in 
the grad lab at 340 JBE), Zip drives, floppy drives (if any of those are 
left), and printers.  Then, at last, the pirates will be defeated, or will 
they?  Mr. Perrone may still lie awake at night knowing that someone might 
figure out a way to use USB or parallel ports or even Van Eck phreaking or 
some other electromagnetic conduit to smuggle copyrighted data out 
(presumably the library computers, at least, will still have the capability 
to display such work, if UCSC intends to continue to function as a 

   I wish I had the time and energy to take these people on, but I'm in the 
final stages of my thesis and I work full-time.  I still suspect this was all 
caused by a vague threat from the RIAA/MPAA.  I was on campus on Fri. 
afternoon and the network was blazing fast (both within and without), so I 
fail to perceive Mr. Perrone's "urgency."

- ------------------------------------------------------------
|  John Callaway      |  www.cse.ucsc.edu/~callaway/       |
|  Software Engineer  |  VisiComp, Inc.  www.visicomp.com  |
- ------------------------------------------------------------
PGP public key fingerprint
   ( John Callaway <john.callaway@visicomp.com> ):
83FC 5E0B B650 7D92 796F  EC27 BC6E AC0B 9AAD 5B69

On Saturday 11 May 2002 20:18, Rick Moen wrote:
> So, John C., it's possible that my earlier point was somehow unclear.
> Just in case of that, let's try again:
> The SoE Computing Director, Mr. Perrone, claims it's going after certain
> peer-to-peer filesharing protocols because they're used to "share
> copyrighted material", by which he means share copyrighted material
> whose usage terms do not permit that.
> However, by far the most common peer-to-peer file sharing protocol in
> general usage -- including for illegal publication of music, movies, and
> propiatary software -- is MS-Windows file sharing.
> Just to be crystal-clear about what I'm talking about, I mean the "File
> and Print Sharing" feature of the Microsoft Network Client, which runs
> either over a NetBEUI, IPX/SPX, or (somewhat adulterated) TCP/IP network
> stack.  This networking protocol is heavily used among Win32 machines on
> campus WANs, and somehow these "zero tolerance" martinet bureaucrats are
> never bright enough to include it in their witchhunts' ban lists.  By
> the same token, they inevitably fail to spot the hypocrisy.
> (Yes, I _do_ mean that this scenario has played out at a number of other
> university campuses.  You might want to talk to Don Marti of Linux
> Journal about that.)
> So, of course, you can point the inconsistency out, politely but
> forcefully:  If Mr. Perrone wants to curry brown-nosing points with
> the Regents about how well he stamps out illegal copying, he'll need
> to _also_ sanction everyone who shares out his "C:" drive on Network
> Neighbourhood.  Make sure you bring this point of logic up as forcefully
> (yet politely) as possible.
> On the record and in public, by the way.  Just sending the guy a letter
> or e-mail after he's already associated himself with a foolish School of
> Engineering policy doesn't do a whole lot of good.

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org