| delorie.com/archives/browse.cgi | search |
On Mar 12 16:13, Dave Korn wrote: > Brian Dessent wrote on 12 March 2008 15:59: > > Dave Korn wrote: > > > Now, who supposes you could work around the restriction by writing > > > > > > * (WORD *) 0x004000dc = POSIX_CUI; > > > > > > just before calling NtSetInformation? > > > > How are you going to fool the executive by poking around in the PE > > header from userspace long after the process has initialized? The > > executive fundamentally knows which subsystem any given process is > > running in because it created it and manages the low level process > > table. > > This is not just any code - this is MS code. > > Given that, it's therefore going to have been done as quickly and cheaply > as possible, so why should we assume they wouldn't they just check the value > in the PE header at the start of NtSetInformationProcess? Is that just an assumption or do you know that this would work? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |