[1] : Jargon File (4.3.1, 29 Jun 2001)

live data n. 1. data that is written to be interpreted and takes over
   program flow when triggered by some un-obvious operation, such as
   viewing it. one use of such hacks is to break security. for example,
   some smart terminals have commands that allow one to download strings to
   program keys; this can be used to write live data that, when listed to
   the terminal, infects it with a security-breaking virus that is
   triggered the next time a hapless user strikes that key. for another,
   there are some well-known bugs in vi that allow certain texts to send
   arbitrary commands back to the machine when they are simply viewed. 2.
   in c code, data that includes pointers to function hooks executable
   code. 3. an object, such as a trampoline, that is constructed on the
   fly by a program and intended to be executed as code.


see also:
virus vi hook trampoline 

[2] : The Free On-line Dictionary of Computing (27 SEP 03)

live data
     
        1. data that is written to be interpreted and takes over
        program flow when triggered by some un-obvious operation, such
        as viewing it.  one use of such hacks is to break security.
        for example, some smart terminals have commands that allow one
        to download strings to program keys; this can be used to write
        live data that, when listed to the terminal, infects it with a
        security-breaking virus that is triggered the next time a
        hapless user strikes that key.  for another, there are some
        well-known bugs in vi that allow certain texts to send
        arbitrary commands back to the machine when they are simply
        viewed.
     
        2. in c, data that includes pointers to functions
        executable code.
     
        3. an object, such as a trampoline, that is constructed on
        the fly by a program and intended to be executed as code.
     
        4. actual real-world data, as opposed to "test data".  for
        example, "i think i have the record deletion module finished."
        "have you tried it out on live data?"  this usage usually
        carries the connotation that live data is more fragile and
        must not be corrupted, or bad things will happen.  so a more
        appropriate response to the above claim might be: "well, make
        sure it works perfectly before we throw live data at it."  the
        implication here is that record deletion is something pretty
        significant, and a haywire record-deletion module running amok
        on live data would probably cause great harm.
     
        jargon file
     
     
see also:
virus vi c trampoline jargon file 

Data >> D Words
Data, definition of term: Data
data_pag1.html

Data Rate >> D Words
Data Rate, definition of term: Data Rate
data+rate_pag1.html

Data Glove >> D Words
Data Glove, definition of term: Data Glove
data+glove_pag1.html

Data Mining >> D Words
Data Mining, definition of term: Data Mining
data+mining_pag1.html

Data Path >> D Words
Data Path, definition of term: Data Path
data+path_pag1.html

Data Point >> D Words
Data Point, definition of term: Data Point
data+point_pag1.html

Data Set >> D Words
Data Set, definition of term: Data Set
data+set_pag1.html

Data Model >> D Words
Data Model, definition of term: Data Model
data+model_pag1.html

Data Flow >> D Words
Data Flow, definition of term: Data Flow
data+flow_pag1.html

Data Communicat >> D Words
Data Communicat, definition of term: Data Communicat
data+communicat_pag1.html

Page 1 2 Next