Wrong.Quote:
At the kernel level all you can really do is crash the system.
wrong agian. And you contradict your own post with those two sentences, at that.Quote:
You need to be in the user/applications layer to cause mahem.
Printable View
Wrong.Quote:
At the kernel level all you can really do is crash the system.
wrong agian. And you contradict your own post with those two sentences, at that.Quote:
You need to be in the user/applications layer to cause mahem.
Nope,
Assuming a 4-ring system, the kernel (ring0) will only run low level. Drivers will run in 1 and 2 along with other system applications; but USER APPLICATIONS will only run in ring3
It is only in ring3 that you will find the user passwords and banking details ;)
Right, the higher up the tier the more access you have. All the way up to the point of direct hardware access.Quote:
Assuming a 4-ring system, the kernel (ring0) will only run low level. Drivers will run in 1 and 2 along with other system applications; but USER APPLICATIONS will only run in ring3
WTF?! Its like a brain-farting diarrea explosion in this thread.Quote:
It is only in ring3 that you will find the user passwords and banking details
T-Spec is right on this one. I think you are confusing processor rings with actual physical locations nihil >.< The rings of a processor is simply a hierarchical protection mechanism. They are simply layers of privileges with ring0 being the most privy to system resources. Special gates between these layers, called rings, are the way in which higher numbered, lesser privileged, rings gain access to the more privy rings and are done in a predefined manner.