The reason I ask is because the einstein client in the freash ports is not the current one with boinc. No new work is being assigned. They sugested or asked if I could run boinc 6.10.17 linux in emulation and if so, I would be able to crunch einstein data.
Hi All,
I want to write a domain specific REST/HTTP server to run on FreeBSD. I have control over both the server side and the primary client intended to consume the service.
My question is: how do you think it should be designed to support multiple connections, given:
It will run on a... (6 Replies)
I used to use x86 Linux clients for this years ago, but ceased all activity until last night. I have resurrected an old Sun Blade 100, which used to run Solaris 9, when I first owned it, in the 2003 period, but now is very much alive with 2 gig of new ram, and and extra 10 gig of drive space... (0 Replies)
Hi guys, so, I have a server running an sqlite database which is accessed by many client machines working as hardware testers, whenever something fails and needs to be replaced the operator would have to enter the Serial Number of the part being replaced as well as some other data. and... (0 Replies)
Ok, I've been shopping around and I've seen some nice one's, but they are either too expensive or they are not 64-bit; I want to be prepared for the future at the right price (under $3,000 with a decent configuration)! :D
Where can I find a good 64-bit desktop or workstation that will run the... (0 Replies)
Hi Every One,
I got a Basic doubts about clients on X-Server environment.
1) First of all what is mend by one client. (as per my understanding one application which is connected to X-server).
2) if i say two clients connected to my X-Server from the same machine, does it mean that two... (0 Replies)
Hello all!
I have been using FreeBSD for years, however, I have colleagues who prefer Linux. For some reason we can never meet eye to eye on what the advantage is from one system to the other.
My question is, can anyone explain what the differences are between both systems in respect to each... (1 Reply)
boinc_selinux(8) SELinux Policy boinc boinc_selinux(8)NAME
boinc_selinux - Security Enhanced Linux Policy for the boinc processes
DESCRIPTION
Security-Enhanced Linux secures the boinc processes via flexible mandatory access control.
The boinc processes execute with the boinc_t SELinux type. You can check if you have these processes running by executing the ps command
with the -Z qualifier.
For example:
ps -eZ | grep boinc_t
ENTRYPOINTS
The boinc_t SELinux type can be entered via the boinc_exec_t file type.
The default entrypoint paths for the boinc_t domain are the following:
/usr/bin/boinc_client
PROCESS TYPES
SELinux defines process types (domains) for each process running on the system
You can see the context of a process using the -Z option to ps
Policy governs the access confined processes have to files. SELinux boinc policy is very flexible allowing users to setup their boinc pro-
cesses in as secure a method as possible.
The following process types are defined for boinc:
boinc_t, boinc_project_t
Note: semanage permissive -a boinc_t can be used to make the process type boinc_t permissive. SELinux does not deny access to permissive
process types, but the AVC (SELinux denials) messages are still generated.
BOOLEANS
SELinux policy is customizable based on least access required. boinc policy is extremely flexible and has several booleans that allow you
to manipulate the policy and run boinc with the tightest access possible.
If you want to allow boinc_domain execmem/execstack, you must turn on the boinc_execmem boolean. Enabled by default.
setsebool -P boinc_execmem 1
If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default.
setsebool -P daemons_dump_core 1
If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default.
setsebool -P daemons_enable_cluster_mode 1
If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default.
setsebool -P daemons_use_tcp_wrapper 1
If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default.
setsebool -P daemons_use_tty 1
If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by
default.
setsebool -P deny_ptrace 1
If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default.
setsebool -P domain_fd_use 1
If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by
default.
setsebool -P domain_kernel_load_modules 1
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default.
setsebool -P global_ssp 1
If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default.
setsebool -P nscd_use_shm 1
PORT TYPES
SELinux defines port types to represent TCP and UDP ports.
You can see the types associated with a port by using the following command:
semanage port -l
Policy governs the access confined processes have to these ports. SELinux boinc policy is very flexible allowing users to setup their
boinc processes in as secure a method as possible.
The following port types are defined for boinc:
boinc_client_port_t
Default Defined Ports:
tcp 1043
udp 1034
boinc_port_t
Default Defined Ports:
tcp 31416
MANAGED FILES
The SELinux process type boinc_t can manage files labeled with the following file types. The paths listed are the default paths for these
file types. Note the processes UID still need to have DAC permissions.
boinc_log_t
/var/log/boinc.log.*
boinc_project_var_lib_t
/var/lib/boinc/slots(/.*)?
/var/lib/boinc/projects(/.*)?
boinc_tmp_t
boinc_tmpfs_t
boinc_var_lib_t
/var/lib/boinc(/.*)?
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/var/run/crm(/.*)?
/var/run/cman_.*
/var/run/rsctmp(/.*)?
/var/run/aisexec.*
/var/run/heartbeat(/.*)?
/var/run/cpglockd.pid
/var/run/corosync.pid
/var/run/rgmanager.pid
/var/run/cluster/rgmanager.sk
root_t
/
/initrd
FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type.
You can see the context of a file using the -Z option to ls
Policy governs the access confined processes have to these files. SELinux boinc policy is very flexible allowing users to setup their
boinc processes in as secure a method as possible.
EQUIVALENCE DIRECTORIES
boinc policy stores data with multiple different file context types under the /var/lib/boinc directory. If you would like to store the
data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under
the /srv dirctory you would execute the following command:
semanage fcontext -a -e /var/lib/boinc /srv/boinc
restorecon -R -v /srv/boinc
STANDARD FILE CONTEXT
SELinux defines the file context types for the boinc, if you wanted to store files with these types in a diffent paths, you need to execute
the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t boinc_exec_t '/srv/boinc/content(/.*)?'
restorecon -R -v /srv/myboinc_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for boinc:
boinc_exec_t
- Set files with the boinc_exec_t type, if you want to transition an executable to the boinc_t domain.
boinc_initrc_exec_t
- Set files with the boinc_initrc_exec_t type, if you want to transition an executable to the boinc_initrc_t domain.
boinc_log_t
- Set files with the boinc_log_t type, if you want to treat the data as boinc log data, usually stored under the /var/log directory.
boinc_project_tmp_t
- Set files with the boinc_project_tmp_t type, if you want to store boinc project temporary files in the /tmp directories.
boinc_project_var_lib_t
- Set files with the boinc_project_var_lib_t type, if you want to store the boinc project files under the /var/lib directory.
Paths:
/var/lib/boinc/slots(/.*)?, /var/lib/boinc/projects(/.*)?
boinc_tmp_t
- Set files with the boinc_tmp_t type, if you want to store boinc temporary files in the /tmp directories.
boinc_tmpfs_t
- Set files with the boinc_tmpfs_t type, if you want to store boinc files on a tmpfs file system.
boinc_unit_file_t
- Set files with the boinc_unit_file_t type, if you want to treat the files as boinc unit content.
boinc_var_lib_t
- Set files with the boinc_var_lib_t type, if you want to store the boinc files under the /var/lib directory.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use
the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels.
COMMANDS
semanage fcontext can also be used to manipulate default file context mappings.
semanage permissive can also be used to manipulate whether or not a process type is permissive.
semanage module can also be used to enable/disable/install/remove policy modules.
semanage port can also be used to manipulate the port definitions
semanage boolean can also be used to manipulate the booleans
system-config-selinux is a GUI tool available to customize SELinux policy settings.
AUTHOR
This manual page was auto-generated using sepolicy manpage .
SEE ALSO selinux(8), boinc(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8), boinc_project_selinux(8), boinc_project_selinux(8)boinc 14-06-10 boinc_selinux(8)