HP3000-L Archives

April 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Mon, 8 Apr 2002 12:19:24 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
donna after me:
> > The current implementation only lets you see "user" variables
> > and not "HP" variables[...]

> why is that?  (i'm asking hp, not gavin :-)  it seems so strange
> to not be able to see something that i (as the system manager) can't
> change.....so i'm not seeing a security risk nor a 'de-stablization'
> risk.

The user variables are certainly literal data stored in a data structure
which can be hunted down and read from another session.  Most/all of the
(real) "HP" variables are, I believe, "virtual" variables (HPCPUSECS for
example) where what's (probably) stored in the "variable table" is the
address of the function to be called to calculate and return the current
value.

So getting at virtual "HP" variables from another session would require
calling the appropriate function from the context of the remote session
which is hard or impossible to do.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2