full-disclosure - Cisco's stolen code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: dufresne at winternet.com (Ron DuFresne)
Subject: Cisco's stolen code 

On Tue, 25 May 2004, Ng, Kenneth (US) wrote:

> Brian: I will give you another good reason to not go near the stolen code.
> If you EVER want to work on any project that is even remotely related to
> routers, or routing or anything else that Cisco equipment can do, you can
> not have touched any of the stolen code, or your code will be suspect.
> (Your accounting package has queues?  Cisco IOS has queues (I assume), you
> must have copied it.)  Even if your writing the code entirely from scratch,
> because you have seen the stolen code, you may be suspect.  Is it unfair?
> Definitely.  But this is why the GNU people emphasize staying away from any
> licensed source code.

Well except all that code stoen from SCO <grin>...


Thanks,

Ron DuFresne
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cutting the space budget really restores my faith in humanity.  It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
	***testing, only testing, and damn good at it too!***

OK, so you're a Ph.D.  Just don't touch anything.