计算机网络安全与管理：第17讲 软件安全.pptVIP

* * Another topic of concern is management of access to common, shared memory by several processes, or threads within a process. Without suitable synchronization of accesses, it is possible that values may be corrupted, or changes lost, due to overlapping access, use and replacement of shared values. The resulting race condition occurs when multiple processes and threads compete to gain uncontrolled access to some resource. This problem is a well-known and documented issue that arises when writing concurrent code, whose solution requires the correct selection and use of appropriate synchronization primitives. Even so, it is neither easy nor obvious what the most appropriate and efficient choice is. If an incorrect sequence of synchronization primitives is chosen, it is possible for the various processes or threads to deadlock, each waiting on a resource held by the other. There is no easy way of recovering from this flaw without terminating one or more of the programs. An attacker could trigger such a deadlock in a vulnerable program to implement a denial of service upon it. In large complex applications, ensuring that deadlocks are not possible can be very difficult. Care is needed to carefully design and partition the problem to limit areas where access to shared memory is needed, and to determine the best primitives to use. * The third component of our model of computer programs is that it executes on a computer system under the control of an operating system (O/S). This aspect of a computer program is often not emphasized in introductory programming courses, however from the perspective of writing secure software it is critical. Excepting dedicated embedded applications, in general, programs do not run in isolation on most computer systems. Rather, they run under the control of an operating system that mediates access to the resources of that system, and shares their use between all the currently executing programs. The operating system constructs an execution