Sponsored Content
Top Forums UNIX for Advanced & Expert Users snort installation on freebsd issues Post 34143 by xyyz on Thursday 6th of February 2003 07:29:43 PM
Old 02-06-2003
the resolution was a simple one.

i needed to enter the following command within /usr/ports/security/snort

make expand

this gave me all the directories that were needed.

how i'm having another issue.

when i try to start apache the way they want me to, apachectl start (or restart), i get the following error:

/usr/local/sbin/apachectl start: httpd could not be started

i have no clue where to begin. i checked the path in the script to see if it was pointing to the proper location for httpd, and it is. so i'm completely confused.
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

FreeBSD 4.7 X issues - assistance req'd please

question: i just installed FreeBSD 4.7 on my laptop, when i log in as root, i can startx no problem at all but when i try to start it as a user, i can't. otiginally it told me i needed to be a member of the group 'wheel' to do startx, no problem, added myself in /etc/group, but for some reason i... (1 Reply)
Discussion started by: Calum
1 Replies

2. UNIX for Dummies Questions & Answers

Some FreeBSD issues

I have been using Linux for 3 years now, and I think I am getting enough knowledge (and confidence) to try some more 'traditional' unix variants. I installed FreeBSD 5.0-CURRENT. I have a couple of questions for the time being: 1) Frequently when I need to compile software packages they can't... (16 Replies)
Discussion started by: cbkihong
16 Replies

3. Linux

freeBSD installation

why is my new freeBSD hanging at setting up hostname each time I plug in the network cable i use host name like X.ng I intend to configure it as a gateway (2 Replies)
Discussion started by: AkinOkin
2 Replies

4. BSD

FreeBSD - Kernel Queries/Issues

All, I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server. I managed to fix it by doing the following: Booting into loader mode: unload set... (3 Replies)
Discussion started by: drbabbers
3 Replies

5. Web Development

Using IP.Board on FreeBSD, having SQL/Apache Issues

Server: FreeBSD 7.2-RELEASE MYSQL Version: MYSQL 5.1.36 PHP Version: 5.2.10 (apache2handler) IP.Board Version: v3.0.2 Safe Mode: OFF For the most part previously IP.Board, forum software, has run fine without any issues. Regular web pages and .php pages seem to load fine without any issues.... (2 Replies)
Discussion started by: Dark Severance
2 Replies

6. UNIX for Dummies Questions & Answers

Resolved: htpasswd issues (-b) on FreeBSD

I wrote a script to batch-create directories with .htaccess and .htpasswd files. I am using the following line to create the .htpasswd file: htpasswd -cb .htpasswd $USER $PASS However, I keep getting this message in return: Usage: htpasswd passwordfile username The -c flag creates a new... (1 Reply)
Discussion started by: Spetnik
1 Replies

7. BSD

FreeBSD AMD NFS over TCP issues

Hi! I have a major issue with FreeBSD 7.1 i386. We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp. Now I cant mount homedirs since NFS/AMD seem to fallback to udp :( Trying to force it with amd options nfs_proto=tcp and so on. ... (0 Replies)
Discussion started by: Esaia
0 Replies

8. AIX

Networking Issues - Opera, FreeBSD, AIX

(1) Hi, Am working on FreeBSD 7.4/i386 and installed Opera 11.01 through ports collection manually... But when I run first time am getting "opera: cannot connect X server. Error: Unknown error: 0" What is this error all about???? Please help me to sort out this issue!!! (2) Hi, currently am... (12 Replies)
Discussion started by: Priya Amaresh
12 Replies

9. Homework & Coursework Questions

Error in installation of Snort 2.97.0

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: My system is Redhat 5.6. I want to install snort in my system which requires following dependencies. 1. Libpcap... (8 Replies)
Discussion started by: Ankur Goyal
8 Replies

10. BSD

FreeBSD DHCP wpa_supplicant Wi-Fi Issues

I just got FreeBSD up and running with an XFCE desktop on an old Gateway laptop. It works great, except the wireless setup is scaring me. I can connect to my home WiFi fine most of the time, but I'm concerned about other WiFi that I will need to connect to away from home. I understand that I can... (1 Reply)
Discussion started by: BrentBANKS
1 Replies
snort_selinux(8)					       SELinux Policy snort						  snort_selinux(8)

NAME
snort_selinux - Security Enhanced Linux Policy for the snort processes DESCRIPTION
Security-Enhanced Linux secures the snort processes via flexible mandatory access control. The snort processes execute with the snort_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 snort_t ENTRYPOINTS
The snort_t SELinux type can be entered via the snort_exec_t file type. The default entrypoint paths for the snort_t domain are the following: /usr/bin/snort, /usr/sbin/snort, /usr/sbin/snort-plain 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 snort policy is very flexible allowing users to setup their snort pro- cesses in as secure a method as possible. The following process types are defined for snort: snort_t Note: semanage permissive -a snort_t can be used to make the process type snort_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. snort policy is extremely flexible and has several booleans that allow you to manipulate the policy and run snort with the tightest access possible. 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. Disabled by default. setsebool -P nscd_use_shm 1 MANAGED FILES
The SELinux process type snort_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. 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 prelude_spool_t /var/spool/prelude(/.*)? /var/spool/prelude-manager(/.*)? root_t / /initrd snort_log_t /var/log/snort(/.*)? snort_tmp_t snort_var_run_t /var/run/snort.* 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 snort policy is very flexible allowing users to setup their snort processes in as secure a method as possible. STANDARD FILE CONTEXT SELinux defines the file context types for the snort, 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 snort_etc_t '/srv/snort/content(/.*)?' restorecon -R -v /srv/mysnort_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for snort: snort_etc_t - Set files with the snort_etc_t type, if you want to store snort files in the /etc directories. snort_exec_t - Set files with the snort_exec_t type, if you want to transition an executable to the snort_t domain. Paths: /usr/bin/snort, /usr/sbin/snort, /usr/sbin/snort-plain snort_initrc_exec_t - Set files with the snort_initrc_exec_t type, if you want to transition an executable to the snort_initrc_t domain. snort_log_t - Set files with the snort_log_t type, if you want to treat the data as snort log data, usually stored under the /var/log directory. snort_tmp_t - Set files with the snort_tmp_t type, if you want to store snort temporary files in the /tmp directories. snort_var_run_t - Set files with the snort_var_run_t type, if you want to store the snort files under the /run or /var/run 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 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), snort(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) snort 14-06-10 snort_selinux(8)
All times are GMT -4. The time now is 04:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy