This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Following Chris' new signal handling approach and the previous patch "Giving access to pinfo after seteuid and exec", we can now turn pinfo security on. It's just a matter of removing the FILE_MAP_WRITE permission for Everybody, and a couple of useless PID_MAP_WRITE in pinfo constructors. I have left the PID_MAP_WRITE in the winpids constructors for now, they will be removed later. Pierre 2003-09-26 Pierre Humblet <pierre.humblet@ieee.org> * pinfo.cc (pinfo::init): Do not give FILE_MAP_WRITE access to Everybody. * exceptions.cc (sig_handle_tty_stop): Do not create pinfo parent with PID_MAP_WRITE. * fhandler_process.cc (fhandler_process::fill_filebuf): Ditto for pinfo p. * signal.cc (kill_worker): Ditto for pinfo dest.
Attachment:
pinfo3.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |