Date: Mon, 20 Sep 1999 11:05:40 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: kiril@ideaglobal.com (Kiril Mitev) Cc: ark@eltex.ru, security@FreeBSD.ORG Subject: Re: Real-time alarms Message-ID: <199909201805.LAA59995@gndrsh.dnsmgr.net> In-Reply-To: <199909201600.QAA31235@loki.ideaglobal.com> from Kiril Mitev at "Sep 20, 1999 04:00:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Ouch. > > > > > > do you REALLY suggest things along the lines > > > > > > set proc/priv=(... , .... , .... ) > > > > Yes, at least the functionality, we don't have to use the VMS DCL > > interface to it. set proc/priv= just flips bits in the process > > header area. > > IIRC, it 'flips bits' in a dedicated VAXCPU register. You surely don't really know how it works if you think that. It sets bits in the process header area, or PCB. It does not directly set bits in any dedicated CPU register. Some process priviledges do effect what bits in the CPU you can fool with, like CMKRN allows your user land code to execute as if it was running in kernel mode. Basically your user code tries to do a Change Mode to Kernel instruction, VMS traps that, looks at your PCB, goes, ohh, okay he is allowed to do that, sets the bits in the register for you faking the instruction and returning to your code. > > > You have a better idea?? > > NO, so I will voluntarily shut up . :-). No need to do that, just find me a better idea!! I am open to anything, need more input.. need more input... need more COFFEE!!! -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909201805.LAA59995>