07-08-2013
Looking for PCI Compliance tool for Redhat Lix.
Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password.
This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies
2. UNIX for Dummies Questions & Answers
In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this:
1. Options outside any brackets are mandatory
2. Options inside these < .. > are mandatory too
3. Options inside ... (4 Replies)
Discussion started by: vkleban
4 Replies
3. Red Hat
Hello
I have been asked to provide a security patch analysis of servers in my environment. For HPUX and Solaris there are tools wich can be loaded onto the servers to do this. However I do not know of one for Redhat . At this point I must mentioned that the Redhat servers are behind a firewall... (2 Replies)
Discussion started by: dmsmith32
2 Replies
4. Cybersecurity
From the nessus scanner tool report i got below vulnerability
PCI DSS Compliance : Insecure Communication Has Been Detected
http://www.tenable.com/plugins/index.php?view=single&id=56208
As per the description given in above link - I am not able to understand
How to find insecure port... (2 Replies)
Discussion started by: saurabh84g
2 Replies
5. Shell Programming and Scripting
Hi,
I want to monitor any new file to be created in some of the directory using inotifywait tool but this is not available in Redhat 5.6.
Could you please let me know how to achieve (monitoring of file) without using inotifywait too? Because i dnt want to install this tool due to some reason.... (1 Reply)
Discussion started by: Pawan Kumar
1 Replies
6. HP-UX
I need to set password compliance for some servers in my company.
However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are :
System Users: i.e root, etc
Batch/Application Users: oracle, bscs, etc
Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies
7. OS X (Apple)
Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days.
I have written a program that is an Egg Timer with simple animation.
I now realise how sophisticated 'bash' is compared to full posix compliance.
The code below has passed all of the tests from... (11 Replies)
Discussion started by: wisecracker
11 Replies
LICQ(1) General Commands Manual LICQ(1)
NAME
licq - ICQ client
SYNOPSIS
licq [OPTION]... [-- PLUGIN-OPTIONS]...
DESCRIPTION
licq is an ICQ instant messaging client daemon that supports a number of interfaces via plug-ins, primarily Qt, but also GTK+, console, and
other utility plug-ins. At least one plug-in is required for Licq to function.
OPTIONS
-b DIR Set the base directory for configuration and data files (default: $HOME/.licq)
-c Disable color at standard output.
-d NUMBER
Set what information is logged to standard output:
1 - status information
2 - unknown packets
4 - errors
8 - warnings
16 - all packets
Add values together for multiple options.
-h Print a help screen on standard output, then exit.
-I Force initialization of the given base directory.
-o FILE
Redirect standard error to FILE, which can be a device (e.g., /dev/ttyp4).
-p PLUGIN
Load the given plug-in library.
EXAMPLES
To start licq with the KDE GUI plug-in:
licq -p kde-gui
This choice is recorded, so next time it suffices to start without any options.
FILES
$HOME/.licq/
per-user configuration data
AUTHOR
This man page was written by Zed Pobre <zed@debian.org> and Peter Eisentraut <petere@debian.org> for the Debian project.
08 Oct 2006 LICQ(1)