Re: Securing code in embedded devices

From: CBFalconer (cbfalconer_at_yahoo.com)
Date: 02/15/05

  • Next message: Zach: "Re: Critical error 101 on MS AntiSpyware install" 
    Date: Tue, 15 Feb 2005 06:02:09 GMT

    "Nicholas O. Lindan" wrote:
    >
    ... snip ...
    >
    > The most successful companies publish the source code for their
    > products. Published schematics are SOP for h/p^H^H^HAgilent, IBM,
    > Tektronix, consumer products etc. etc. etc..

    I heartily agree. One problem is that some of the code, and some
    of the circuitry, of commercial products are so bad that their
    owners would be embarassed by publication. It happends in the
    public domain world too - someone publishes a binary and hides the
    embarassing source. That was the fate of NULU in the CP/M world
    25+ years ago, for example. Everybody used it. About the same
    time I published LT, and I believe that is still going. 

    -- 
"If you want to post a followup via groups.google.com, don't use
 the broken "Reply" link at the bottom of the article.  Click on 
 "show options" at the top of the article, then click on the 
 "Reply" at the bottom of the article headers." - Keith Thompson
  • Next message: Zach: "Re: Critical error 101 on MS AntiSpyware install"

    Relevant Pages

    • Re: Securing code in embedded devices
      ... > The most successful companies publish the source code for their ... Published schematics are SOP for h/p^H^H^HAgilent, IBM, ... public domain world too - someone publishes a binary and hides the ... the broken "Reply" link at the bottom of the article. ...
      (comp.arch.embedded)
    • Re: x86 Stack Confusion
      ... If the source code reads "writeln" it is expanded, in the compiler, to ... A similar process applies to writewhich expands to "write; ... The compiler calls the appropriate i/o routine for the type, so a linkage is likely to show such things as writeint, writereal, writestring, etc. ... "If you want to post a followup via groups.google.com, don't use the broken "Reply" link at the bottom of the article. ...
      (comp.lang.c)
    • Re: Visual SourceSafe considered harmful
      ... > The bottom line is one works with what's at hand and you deal with it. ... > tier application huge projects and never had one problem of source code ... It may be that VSS has some nasty corner ... it, but I always keep my own full copy of the source tree on a drive, ...
      (comp.programming)
    • Re: function call with arguments which takes no arguments
      ... There should NEVER be a function prototype in a source code ... >> source code file. ... Those rules don't affect the type information in the slightest. ... the broken "Reply" link at the bottom of the article. ...
      (comp.arch.embedded)
    • Re: The Public Domain
      ... > Public domain software is software that is not copyrighted. ... > source code is not available. ... You have all the rights to do anything you want with that executable. ... A scheme guaranteed to keep lawyers employed. ...
      (alt.lang.asm)