RE: [Full-Disclosure] Cisco's stolen code

From: Ng, Kenneth (US) (kenng_at_kpmg.com)
Date: 05/27/04

  • Next message: Kurt Lieber: "[Full-Disclosure] [ GLSA 200405-23 ] Heimdal: Kerberos 4 buffer overflow in kadmin"
    To: "'Azerail'" <Azerail@supersecretninjaskills.com>, full-disclosure@lists.netsys.com
    Date: Thu, 27 May 2004 09:08:24 -0400
    
    

    Assuming the book is legally published with the source code belonging to the
    author, or proper permissions obtained, reading a book should not be a
    problem. Otherwise, college courses would also be illegal. Unless that is
    what people like SCO want.

    -----Original Message-----
    From: full-disclosure-admin@lists.netsys.com
    [mailto:full-disclosure-admin@lists.netsys.com]On Behalf Of Azerail
    Sent: Thursday, May 27, 2004 6:02 AM
    To: full-disclosure@lists.netsys.com
    Subject: Re: [Full-Disclosure] 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.

    So much for reading a book on code then. How sad.

    Azerail

    -- 
    "All great truths begin as blasphemies" 
    		-- George Bernard Shaw
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html
    *****************************************************************************
    The information in this email is confidential and may be legally privileged.
    It is intended solely for the addressee. Access to this email by anyone else
    is unauthorized. 
    If you are not the intended recipient, any disclosure, copying, distribution
    or any action taken or omitted to be taken in reliance on it, is prohibited
    and may be unlawful. When addressed to our clients any opinions or advice
    contained in this email are subject to the terms and conditions expressed in
    the governing KPMG client engagement letter.         
    *****************************************************************************
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html
    

  • Next message: Kurt Lieber: "[Full-Disclosure] [ GLSA 200405-23 ] Heimdal: Kerberos 4 buffer overflow in kadmin"

    Relevant Pages

    • Re: Request For Reviewers
      ... computer instead of reading from a book kind of defeats the purpose, ... really cannot be made without a multi-page chunk of source code, ... serves no other purpose than pleasing a fictitious compiler and/or tester. ...
      (borland.public.delphi.non-technical)
    • Re: rsync / Include only
      ... In comp.os.linux.misc iforone: ... like reading the source code for every program I have a problem with. ... I must restrain myself and refrain from further ...
      (comp.os.linux.misc)
    • Re: Sement fault
      ... > %someletter that many put after the commands? ... have to download/install the source code and wander through it looking ... or reading the code to find out what it does. ... Open standards. ...
      (alt.os.linux.suse)
    • Re: Help, where to start learning Java
      ... Maintainig programs often begins by reading code ... > To learn to read source code, ... > "Learning to read Java". ...
      (comp.lang.java.programmer)