Commit Graph

11 Commits

Author SHA1 Message Date
mycroft 4862b84c92 Add RCS identifiers (this time on the correct side of the branch), and
incorporate recent changes in netbsd-0-9 branch.
1993-08-01 19:22:24 +00:00
mycroft 97cae397ee Finish moving struct definitions outside of function declarations. 1993-07-17 15:24:33 +00:00
cgd 4b90229cd2 do the "right thing" with mmap protections, once and for all.
in particular, if an object is mapped private, DO NOT grant
VM_PROT_ALL protections to it; it could be sensitive data.
1993-07-15 14:48:37 +00:00
cgd b99e3b6666 get rid of bogus protections chacking which conflicts w/guido's
patch...
1993-07-07 11:25:32 +00:00
cgd cc5e8e00d5 add rcs ids and clean up headers 1993-05-20 03:59:08 +00:00
cgd fd7c50fd61 patch from Pete Chown <pc123@cus.cam.ac.uk> to fix mmap
modes vs. read/write permissions problem.
1993-05-07 01:58:11 +00:00
glass 33d009a09c Prevents you from creating double faults and such mmaping stuff on top
of the kernel, etc. Tested.  Derived from BSDI public patches
1993-04-10 15:06:01 +00:00
cgd 4493ba8058 fixed stupid typo (missing comma) in hand-applied diff 1993-04-09 17:19:02 +00:00
cgd a128c34f9c From: Guido van Rooij <guido@gvr.win.tue.nl>
when mmapping a file, permissions are checked as it should be. When
mprotect()-ing the address range afterwards, no protection was checked
regarding the protection of the file originally opened. So
when you open /usr/bin/su RDONLY and SHARED you could afterwards change
the mmapped region to READ|WRITE. This gave the possibility to obtain
root privs obviously.
1993-04-09 17:16:30 +00:00
cgd 202313150e changes, running on sef's machine to good effect, likely contributed
by torek.  (sef told me to get them, and their origin...)
1993-04-09 17:13:17 +00:00
cgd 61f282557f initial import of 386bsd-0.1 sources 1993-03-21 09:45:37 +00:00