boinc(1)boinc(1)NAME
boinc - The BOINC core client program.
SYNOPSIS
boinc [options]
DESCRIPTION
The BOINC "core client", boinc, is the heart of BOINC. It controls which project applications are run on your computer, downloading
"Workunits" and uploading the "Result" files from completed tasks. boinc is usually run in the background, ideally as a daemon. It can then
be controlled either by a graphical tool called the BOINC Manager, boincmgr(1), or a command-line tool called boinccmd(1), by means of Re-
mote Proceedure Calls (RPCs) over port 31416.
The BOINC core client can be controlled by command-line options, configuration files, and environment variables. Standard usage is simply
to start the client running in the background.
OPTIONS
These command-line options for boinc can be used to control how BOINC is started. Once the client has started, you should use a separate
program, (boincmgr(1) or boinccmd(1)) which communicates with it by means of Remote Proceedure Calls (RPCs).
--help show options
--version
show version info
--exit_when_idle
exit when there are no results
--show_projects
show attached projects
--detach_project URL
detach from a project
--reset_project URL
reset (clear) a project
--attach_project URL key
attach to a project
--update_prefs URL
contact a project to update preferences
--run_cpu_benchmarks
run the CPU benchmarks
--check_all_logins
for idle detection, check remote logins too
--allow_remote_gui_rpc
allow remote GUI RPC connections
--gui_rpc_port port
port for GUI RPCs
--redirectio
redirect stdout and stderr to log files
--dir path
use given dir as BOINC home
--no_gui_rpc
Omits creation of a socket as required for the remote control of the client. Consequently the client cannot be controlled by exter-
nal tools like GUIs (boincmgr etc.) or the console command tool (boinccmd).
--daemon
run as daemon
--exit_before_start
exit right before starting a job
--exit_after_finish
exit right after finishing a job
--insecure
disable app sandboxing
--launched_by_manager
core client was launched by Manager
--run_by_updater
set by updater
ACCESS CONTROL FOR GUI RPC
By default the core client accepts GUI RPC connections only from programs on the same host, which means that any user on this host can con-
trol the core client.
SEE ALSO boinccmd(1), boincmgr(1)
<http://boinc.berkeley.edu/wiki/Client_configuration_(advanced)>
COPYRIGHT
Copyright (C) 2007-2008 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
April 06, 2008 boinc(1)
Check Out this Related Man Page
boinc_project_selinux(8) SELinux Policy boinc_project boinc_project_selinux(8)NAME
boinc_project_selinux - Security Enhanced Linux Policy for the boinc_project processes
DESCRIPTION
Security-Enhanced Linux secures the boinc_project processes via flexible mandatory access control.
The boinc_project processes execute with the boinc_project_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_project_t
ENTRYPOINTS
The boinc_project_t SELinux type can be entered via the unlabeled_t, proc_type, file_type, mtrr_device_t, filesystem_type, sysctl_type,
boinc_project_var_lib_t file types.
The default entrypoint paths for the boinc_project_t domain are the following:
all files on the system, /dev/cpu/mtrr, /var/lib/boinc/slots(/.*)?, /var/lib/boinc/projects(/.*)?
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_project policy is very flexible allowing users to setup their
boinc_project processes in as secure a method as possible.
The following process types are defined for boinc_project:
boinc_project_t
Note: semanage permissive -a boinc_project_t can be used to make the process type boinc_project_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_project policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run boinc_project with the tightest access possible.
If you want to deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable
should be reported in bugzilla, you must turn on the deny_execmem boolean. Enabled by default.
setsebool -P deny_execmem 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 control the ability to mmap a low area of the address space, as configured by /proc/sys/kernel/mmap_min_addr, you must turn
on the mmap_low_allowed boolean. Disabled by default.
setsebool -P mmap_low_allowed 1
If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Enabled by default.
setsebool -P secure_mode_insmod 1
If you want to boolean to determine whether the system permits loading policy, setting enforcing mode, and changing boolean values. Set
this to true and you have to reboot to set it back, you must turn on the secure_mode_policyload boolean. Enabled by default.
setsebool -P secure_mode_policyload 1
If you want to allow unconfined executables to make their heap memory executable. Doing this is a really bad idea. Probably indicates a
badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selin-
uxuser_execheap boolean. Disabled by default.
setsebool -P selinuxuser_execheap 1
If you want to allow all unconfined executables to use libraries requiring text relocation that are not labeled textrel_shlib_t, you must
turn on the selinuxuser_execmod boolean. Enabled by default.
setsebool -P selinuxuser_execmod 1
If you want to allow unconfined executables to make their stack executable. This should never, ever be necessary. Probably indicates a
badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selin-
uxuser_execstack boolean. Enabled by default.
setsebool -P selinuxuser_execstack 1
If you want to support X userspace object manager, you must turn on the xserver_object_manager boolean. Enabled by default.
setsebool -P xserver_object_manager 1
If you want to allow ZoneMinder to run su/sudo, you must turn on the zoneminder_run_sudo boolean. Disabled by default.
setsebool -P zoneminder_run_sudo 1
MANAGED FILES
The SELinux process type boinc_project_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.
file_type
all files on the system
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_project policy is very flexible allowing users to setup
their boinc_project processes in as secure a method as possible.
STANDARD FILE CONTEXT
SELinux defines the file context types for the boinc_project, 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_project_tmp_t '/srv/boinc_project/content(/.*)?'
restorecon -R -v /srv/myboinc_project_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for boinc_project:
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(/.*)?
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 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_project(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8)boinc_project 14-06-10 boinc_project_selinux(8)