My understanding of computer systems told me that network ports are just
a memory or register. So memory security should encompass all these
networking stuffs. networking servers are provided by services inside
memory. YOU wrote the right process (with StackGuard?), you got
networking security automagically.
side thread - In a way to create fault-tolerance computing, are we also
creating security problems like stack and buffer overflow leading to a
root shell?
> No. File system security arguably the first line of defense. If you
> don't get it on your disk, it won't get into memory. In reality, as
> any security "expert" will tell you, security is layered. Physical
> security is one layer; network security is another layer; user login
> restrictions are another layer; file system access control is a layer;
> code audit are another layer; canaries or stack guards in code are
> another layer; and so on, ad infinitum.
--
Swiftly. Silently. Invisibly. .~. In Linux we trust.
/ v \
news://news.hkpcug.org /( _ )\ http://www.linux-sxs.org
^ ^
http://www.tuxedo.org/~esr/faqs/smart-questions.html
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
