| |||||||||||||
WeakWeakPosted Jun 2, 2005 20:57 UTC (Thu) by zakaelri (guest, #17928)In reply to: Weak by goaty Parent article: The Integrity Measurement Architecture The trusted computing folk can get around this by prohibiting gdb Presumably, the trusted computing folks would not have gdb installed on a secure machine--gdb is inheirently insecurable from their perspective. The entire suite of dev tools is usually the first thing removed from a secure system. Also, you could use strip to remove the symbols from your binaries. That would make it nigh impossible to find anything with gdb.
(Log in to post comments)
Weak Posted Nov 17, 2005 9:48 UTC (Thu) by pkolloch (subscriber, #21709) [Link] > Also, you could use strip to remove the symbols from your binaries. That would make it nigh impossible to find anything with gdb.
Well, only statically linked stuff, or? Any symbol references to dynamically linked libraries remain clearly visible. Ok, ok, from a strict security point of view, dynamic linking has its own large set of issues.
|
|||||||||||||