Re: [Embedlets-dev] Re: Security

[Gregg G. W. <gr...@sk...>]

>(Having been a system operator for over 5 years learned me the avarage
>programmer is lazy and has not even the slightest idea what impact their
>'design' will have in an operational environment.)

:-) :-) :-)

Many people on this list are engineers, not technicans!  I appreciate your 
experience, just make sure you measure your response to similar stimulous in a 
way that allows everyone to see your concerns (this is something that I don't 
do well, because I get passionate about things that I have had bad experiences 
with too ;-).

I spent 9 years working on and around telephone switching systems.  I designed 
a language and the associated processes that controlled the duplex hardware 
(computer level, and device level) during the software retrofit process 
(replacing the software on a running switch).  When something went wrong, I 
typically had 1 hour to go through 500,000 lines of base code (including 
assembly) to find problems (support calls at 3:00am in the morning).  
Sometimes I had 10 minutes to establish the extent of a problem by pouring 
through the status information and control display screens (at 300 baud) to 
establish what the next step was.  As a matter of fact, I got to do this for 
the Prime Minister of the U.K. so that he could talk to his generals in 
Saudi-Arabia on the day the ground war started in 1990.

Believe me when I say I am well aware of many issues that create headaches for 
persons managing systems.  I won't say I know every issue that you know, but 
that's what's great about this list.  We can utilize everyones expertise to 
make sure we make a really great decision about how to do all this stuff.

visible security and encryption in the APIs: -1
pluggable comms interface that could provide security and connection 
authentication: +1

-----
gr...@cy...  (Cyte Technologies Inc)