| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Debugger |
Hi John! :-) JG> Hmmm, now that'd be an excellent security hole, if it didn't.... ;-) JG> Picture a program setting a breakpoint and either monitoring the JG> caching of the hard drive till it picked up on the password file, JG> or found where the kernel was in memory, and just patched it to allow JG> its self to gain access to the entire system.... A user process could then monitor *when* a specific location is accessed, but it could not read the contents. Anyway, I was wrong in my original statement. If the debug registers were not saved across task switches, a breakpoint triggering inside another process would be delivered to that same process. That process would then probably just crash because it doesn't expect to have to handle a breakpoint (well, I'm not exactly sure how a debugging breakpoint is handed over to the program since it can't have interrupt handlers of its own -- probably via a signal). Ciao Pascal --- Msged/LNX 6.1.1* Origin: SYS 64738 (1:153/401.2) SEEN-BY: 633/267 270 @PATH: 153/401 307 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.