Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!sdd.hp.com!caen!umich!sharkey!rjf001!mudos!mju
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO License security - another flame
Message-ID: <91V712w164w@mudos.ann-arbor.mi.us>
Date: 30 Apr 91 00:49:31 GMT
References: <1165@pemcom.pem-stuttgart.de>
Organization: The Programmer's Pit Stop, +1 313 665 2832
Lines: 21

ralfi@pemcom.pem-stuttgart.de (Ralf U. Holighaus) writes:
> You could do so with SCO, and then usr /etc/brand for the system speci-
> fic files to 'brand' the new system to the new serial numbers.

No, you can't.  "brand" does just what its name implies -- it brands
the file permanently with a serial number.  It's impossible to
re-brand a file.

> On the other side: they obviously paid more attention to security than
> ISC. Or did you read hundreds of news messages concerning 'SCO security

No, they didn't.  They paid more attention to making sure that you
can't illegally copy their software, when they should have been paying
attention to things like X11R4, Motif 1.1, the BSD FFS, symbolic
links, System Vr4.0, a working telnet(1), real HDB UUCP, and commands
like su(1) and cron(1) that work the way I expect them to.

--
Marc Unangst               |
mju@mudos.ann-arbor.mi.us  | "Bus error: passengers dumped"
...!hela!mudos!mju         |