Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0 |
|
#
9e7ebef8 |
| 17-Jul-2004 |
Robert Watson <rwatson@FreeBSD.org> |
gcc now objects to a default label without any contents. Because I want to have a comment present in the default case, add a 'break' to each default case that previously had no actual statements.
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs, release/4.3.0_cvs, release/4.3.0 |
|
#
361515d9 |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Add a comment identifying the "privileged on privileged" scenario.
Obtained from: TrustedBSD Project
|
#
8f6fee75 |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Add inter-process authorization uid regression testing for ktrace().
Obtained from: TrustedBSD Project
|
#
72919d5f |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o s/debug/ptrace/ since shortly there will be tests involving other forms of debugging.
Obtained from: TrustedBSD Project
|
#
bacff58c |
| 12-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Expand inter-process authorization regression test to include signalling with sigsegv as one of the tests. o Teach errno_to_string() about ENOTSUPP.
Obtained from: TrustedBSD Project
|
#
274f7445 |
| 11-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o First pass at an inter-process authorization regression testing suite. This test utility attempts to evaluate the current kernel policy for authorization inter-process activities, currently ptr
o First pass at an inter-process authorization regression testing suite. This test utility attempts to evaluate the current kernel policy for authorization inter-process activities, currently ptrace(), kill(, SIGHUP), getpriority(), and setpriority(). The utility creates pairs of processes, initializes their credential sets to useful cases, and reports on whether the results are in keeping with hard-coded safety expectations.
o Currently, this utility relies on the availability of __setugid(), an uncomitted system call used for managing the P_SUGID bit. Due to continuing discussion of optional regression testing kernel components ("options REGRESSION") I'll hold off on committing that until the discussion has reached its natural termination.
o A number of additional testing factors should be taken into account in the testing, including tests for different classes of signals, interactions with process session characteristics, I/O signalling, broadcast activities such as broadcast signalling, mass priority setting, and to take into group-related aspects of credentials. Additional operations should also be taken into account, such as ktrace, debugging attach using procfs, and so on.
o This testing suite is intended to prevent the introduction of bugs in the upcoming sets of authorization changes associated with the introduction of process capabilities and mandatory access control.
Obtained from: TrustedBSD Project
show more ...
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0 |
|
#
9e7ebef8 |
| 17-Jul-2004 |
Robert Watson <rwatson@FreeBSD.org> |
gcc now objects to a default label without any contents. Because I want to have a comment present in the default case, add a 'break' to each default case that previously had no actual statements.
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs, release/4.3.0_cvs, release/4.3.0 |
|
#
361515d9 |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Add a comment identifying the "privileged on privileged" scenario.
Obtained from: TrustedBSD Project
|
#
8f6fee75 |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Add inter-process authorization uid regression testing for ktrace().
Obtained from: TrustedBSD Project
|
#
72919d5f |
| 13-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o s/debug/ptrace/ since shortly there will be tests involving other forms of debugging.
Obtained from: TrustedBSD Project
|
#
bacff58c |
| 12-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o Expand inter-process authorization regression test to include signalling with sigsegv as one of the tests. o Teach errno_to_string() about ENOTSUPP.
Obtained from: TrustedBSD Project
|
#
274f7445 |
| 11-Apr-2001 |
Robert Watson <rwatson@FreeBSD.org> |
o First pass at an inter-process authorization regression testing suite. This test utility attempts to evaluate the current kernel policy for authorization inter-process activities, currently ptr
o First pass at an inter-process authorization regression testing suite. This test utility attempts to evaluate the current kernel policy for authorization inter-process activities, currently ptrace(), kill(, SIGHUP), getpriority(), and setpriority(). The utility creates pairs of processes, initializes their credential sets to useful cases, and reports on whether the results are in keeping with hard-coded safety expectations.
o Currently, this utility relies on the availability of __setugid(), an uncomitted system call used for managing the P_SUGID bit. Due to continuing discussion of optional regression testing kernel components ("options REGRESSION") I'll hold off on committing that until the discussion has reached its natural termination.
o A number of additional testing factors should be taken into account in the testing, including tests for different classes of signals, interactions with process session characteristics, I/O signalling, broadcast activities such as broadcast signalling, mass priority setting, and to take into group-related aspects of credentials. Additional operations should also be taken into account, such as ktrace, debugging attach using procfs, and so on.
o This testing suite is intended to prevent the introduction of bugs in the upcoming sets of authorization changes associated with the introduction of process capabilities and mandatory access control.
Obtained from: TrustedBSD Project
show more ...
|