PyRAFT brings different aspects of software testing - functionality, performance and security - under the umbrella of a single framework. So, PyRAFT your way through the river of Software Testing!
I have a project tree like that.
after running find command with the -no -empty option, i am able to have a list of non empty directory
DO_MY_SEARCH="find . -type d -not -empty -print0"
MY_EXCLUDE_DIR1=" -e NOT_IN_USE -e RTMAP -e NOT_USEFULL "
echo " " > $MY_TEMP_RESULT_1
while... (2 Replies)
A new project was posted on your project board.
Project title: Bash Shell Tutoring
Estimated Budget:
$50/hr
Start date:
Immediately
Required skills:
Linux, Bash, Shell, UNIX
I work as a datawarehouse designer and developer.
Although I usually stick to the role of an analyst,... (0 Replies)
i have two doubts..
1. what is the use /etc/project file. i renamed this file and when i tried to switch user or login with some user account the login was happening slowly. but when i renamed it to original name it was working fine... why so?
2. unix already has useradd and grouadd for... (4 Replies)
We have a system running ssh. When a user logs in, they do not get the project they are assigned to (they run under "system"). I verify the project using the command "ps -e -o user,pid,ppid,args,project". If you do a "su - username", the user does get the project they are assigned to (and all... (2 Replies)
MAC_TEST(4) BSD Kernel Interfaces Manual MAC_TEST(4)NAME
mac_test -- MAC framework testing policy
SYNOPSIS
To compile the testing policy into your kernel, place the following lines in your kernel configuration file:
options MAC
options MAC_TEST
Alternately, to load the testing module at boot time, place the following line in your kernel configuration file:
options MAC
and in loader.conf(5):
mac_test_load="YES"
DESCRIPTION
The mac_test policy module implements a testing facility for the MAC framework. Among other things, mac_test will try to catch corrupt
labels the system is attempting to destroy and drop to the debugger. Additionally, a set of statistics regarding the number of times various
MAC framework entry points have been called is stored in the security.mac.test sysctl(8) tree.
Label Format
No labels are defined for mac_test.
SEE ALSO mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_none(4), mac_partition(4), mac_portacl(4),
mac_seeotheruids(4), mac(9)HISTORY
The mac_test policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project.
AUTHORS
This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc.
under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program.
BUGS
See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD.
While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by
entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user.
BSD December 1, 2002 BSD