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]

Message-ID: <1085559922.7872.11.camel@coruscant.weisserth.net>
From: tobias at weisserth.de (Tobias Weisserth)
Subject: Cisco's stolen code

Hi Roman,

On Wed, 2004-05-26 at 08:53, roman.kunz@...iusbaer.com wrote:
> now when it hits Cisco, everybody say its a crime lurking for the code or 
> publicating it. BUT when it hit M$ everybody thought, its a great idea to 
> share the stolen source code all over the internet (yes also on FD).

What is true for Cisco is even more true for Microsoft. Stay the hell
away from code that hasn't been licensed for you.

Anybody who touches copyrighted code, be it MS or Cisco or whatever, is
at risk. Why should I want to put myself at risk to solve problems the
copyright holder of the code should solve? If I address a security flaw
in MS code and say a year later I decide to write something that might
attract the attention of MS as a competitor then I'm most certainly
being confronted with accusations like "you took that from our code" and
"you are a thief".

Just think about the repeated accusations against Linus Torvalds who
claims he never took a look at the "Lion's book". Just because the damn
book is there people have to defend against it. So stay the hell away
from code that hasn't been licensed to you.

regards,
Tobias