out:
> Date: Thu, 21 Mar 96 13:03:43 EST
> From: guy
> To: <someone>
> Subject: HOUSTON, WE HAVE A PROBLEM
> Cc: <someone> <someone>
>
>
> Out bound from Salomon: From "Howie Windows" <how@sbi89>
> In bound to Silicon Graphics: To:
hoj...@sgi.com> Subject: sar source code
>
> internet:root 543> wc -l *.[ch]
> 129 sa.h
> 626 sadc.c
> 532 saga.c
> 496 sagb.c
> 45 saghdr.h
> 1463 sar.c
> 220 timex.c
> 3511 total
>
> 3500 lines of source, across seven sources, each clearly labelled:
>
> /* Copyright (c) 1984 AT&T */
> /* All Rights Reserved */
>
> /* THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T */
> /* The copyright notice above does not evidence any */
> /* actual or intended publication of such source code. */
>
> ...followed by another email with a subset of the same source,
> slightly modified, and the proprietary header stripped out.
>
> I hope it didn't flow past AT&T's ISP connections...
[snip]
********** end excerpt from 'Corruption at Salomon Brothers' **********
This transfer of proprietary source code that USED to be owned by AT&T
did not even qualify for action. Salomon legal stated Salomon has a lower
obligation for third-party copyrights than they did for software they
contracted for themselves, like Sybase. Salomon didn't have a UNIX source
license, so obviously the employee had gotten it elsewhere.
In the following statistic, it was the only non-Salomon source code.
We went from zero monitoring of Internet email traffic to...
> On 3/21/96 we had our first security incident report.
>
> By 3/26/96 we had an astonishing 38,000 lines of proprietary source code
> outbound.
>
> We were mentally unprepared. Figuratively we were pulling