Sponsored Content
Full Discussion: Any leads to hardening UNIX
Top Forums UNIX for Dummies Questions & Answers Any leads to hardening UNIX Post 16163 by sdharmap on Tuesday 26th of February 2002 11:36:25 AM
Old 02-26-2002
Thanks for your suggestions!

Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

Hardening Solaris 10

So I've just done my first install of Solaris. I installed it on an x86 system and am now in the processing of figuring out what I need to do to 'harden' it. I've got the Security kit downloaded (jass) but I am not sure what to do with the .tar file. I can't seem to find any easy steps to... (6 Replies)
Discussion started by: flood
6 Replies

2. Solaris

Hardening Solaris

What do we need to do to harden a freshly installed solaris OS? like disable telnet, no ftp for root etc...What all services you need to stop? How to check what ports are open? etc etc....please provide all tips that come to your mind...thanks:) (5 Replies)
Discussion started by: rcmrulzz
5 Replies

3. Solaris

Solaris Hardening - SunJass

Hi guys, Is there any script or program which i can use to verify that my hardening setting is all correct ? Recently i am given a task to make sure my Sun servers are all harden properly though sunjass was already introduced. I need to generate a report to convince my manager that the settings... (0 Replies)
Discussion started by: ahlude
0 Replies

4. SuSE

Hardening Suse11 sp1

Currently we are hardening our Solaris server using the Sun provided Jass Security tool kit. How Can I implement the same security level on SUSE11 SP1? Are there any tools similar/equivalent to Jass for SUSE11 SP1? Tanks and Regards (1 Reply)
Discussion started by: vcfko
1 Replies

5. UNIX for Advanced & Expert Users

SuSe Linux Hardening

We've got a FTP server that's open to the public network and its running on Suse SUSE Linux Enterprise Server 11 (x86_64) SP2 Now, since it's an FTP server I can't disable that service, but how else do I harden this server from attacks from outside? I am thinking of disabling the firewall and... (3 Replies)
Discussion started by: hedkandi
3 Replies

6. Solaris

Need jass hardening documentation

Hi, Where I could find information about "Jass hardening" for Solaris10? Because, I change the /opt/SUNWjass/Files/etc/syslog.conf file. But yet I don't know if I must restart the jass (and how?) or I must to copy /opt/SUNWjass/Files/etc/syslog.conf to /etc/syslog.conf? Thanks for your... (2 Replies)
Discussion started by: hiddenshadow
2 Replies

7. Cybersecurity

C-ICAP Hardening

Does anyone have any experience hardening the c-icap.conf file? Here is the default config file, it has a lot of options; sorry about how long it is. I have removed some entries that were not needed as well, but it is still so long :D. Any help is much appreciated as I have never dealt with ICAP. ... (0 Replies)
Discussion started by: savigabi
0 Replies

8. Linux

Password hardening using pam

Hi We have a requirement to vary the minimum password criteria by the group to which a user belongs. For example a standard user should have a password with a minimum length of 12 and containing a mix of characters whereas an administrator should have a password with a minimum length of 14... (1 Reply)
Discussion started by: gregsih
1 Replies

9. Solaris

Rebooting Windows machine leads to continue sync reset on UNIX

Hello, We have Windows 10 machine connected to Sparc T5440 server via serial cable. We access the server from the Windows 10 machine using putty via serial connection. This allows us to access ILOM and Unix. We have recently noticed that whenever we reboot the windows machine (Windows 10),... (11 Replies)
Discussion started by: jasonu
11 Replies

10. HP-UX

Security hardening for standard HP-UX users

Hi, The standard accounts that are created during the HP-UX installation, eg, bin,adm,daemon,uucp,lp,hpdb and nobody have their own shell. Will there be any impact if we change these user's shell to /bin/false? Like processes get interrupted, files cannot be generated, etc. Regards (3 Replies)
Discussion started by: anaigini45
3 Replies
LAM-HELPFILE(5) 						 LAM FILE FORMATS						   LAM-HELPFILE(5)

NAME
lam-helpfile - LAM help message file DESCRIPTION
The lam-helpfile provides detailed error messages and suggestions for help on how to fix common problems. In many places in LAM, when an error occurs, this help file is consulted to display a detailed message of what the error was and, when possible, suggestions on how to fix the problem. It consists of much of the information from the LAM FAQ (particularly in dealing with getting LAM up and running) At present, the following LAM tools use this help file (it is expected that more will use it in future releases. If you have suggestions for locations where more detailed error messages would be helpful, please let us know): hboot lamboot lamexec lamhalt lamnodes mpicc (hcc) mpiCC (hcp) mpif77 (hf77) mpirun recon tkill tping wipe STRUCTURE AND SYNTAX
The help file is multiple blocks of help text separated by single line delimiters. The delimiter lines are of the format: -*-programname:topicname-*- Where programname is the general name of the program (or group of programs) that this help message applies to, and topicname is the spe- cific topic that this message applies two. The special keyword ALL can be used for either the programname or the topicname in some cases; this is usually a "wildcard" value where little specific information is available. Within the block of the message, lines that begin with a "#" are treated as comments; they are not printed out. Three special escape sequences can be used within the help message: %N Where N is a number from 1 to the number of arguments that the help message is invoked with. The "%N" string is replaced with the value of the Nth argument from the argument list. The arguments are passed from the LAM binaries themselves; they cannot be edited. The comments in the default LAM help file explain how many arguments each message is invoked with, and what each argument is. %perror Shows the result of the Unix perror(3) function. %terror Shows the result of the LAM terror() function, which is essentially a wrapper around the Unix perror(3) function. LOCATION OF HELP FILE
The exact location of the help file is configurable. This allows system administrators and/or users to customize the help file for their particular environment. When LAM attempts to print an error message from the help file, it looks for the help file in the following locations (in order): $LAMHELPFILE $HOME/lam-helpfile $HOME/lam-6.5.8-helpfile $HOME/etc/lam-helpfile $HOME/etc/lam-6.5.8-helpfile $LAMHELPDIR/lam-helpfile $LAMHELPDIR/lam-6.5.8-helpfile $LAMHOME/etc/lam-helpfile $LAMHOME/etc/lam-6.5.8-helpfile $TROLLIUSHOME/etc/lam-helpfile $TROLLIUSHOME/etc/lam-6.5.8-helpfile $SYSCONFDIR/lam-helpfile $SYSCONFDIR/lam-6.5.8-helpfile Note the two variables $LAMHELPFILE and $LAMHELPDIR; these variables can be set according to platform, for example, to provide operating system-specific information, or information specific to particular groups of machines, etc. $SYSCONFIDIR is typically $prefix/etc, where $prefix is the location to where LAM was installed; it was the option supplied to ./configure when LAM was built (or /usr/local/lam-6.5.8, by default). However, note that the value of $SYSCONFDIR can be overridden when LAM is con- figured with the --sysconfdir switch. EXAMPLES
The following is an example customization of the help for the hboot and lamboot programs, when the user supplies a host file name that is not found. -*-boot:open-hostfile-*- %1 could not open the hostfile "%2" for the following reason: %perror Things to check: - ensure that the file exists try "ls -l %2" - ensure that you have read permissions on the file try "cat %2" You may not need to specify a host file at all; the system administrators have defined the all of Beowulf cluster host names in the LAM default host name list. If you wish to use all of the Beowulf nodes, simply execute: %1 -v If you have any problems with LAM, please send mail to: lam-admin@your.domain.com FILES
$LAMHOME/etc/lam-6.5.8-helpfile default LAM help file SEE ALSO
hboot(1), lamboot(1), lamexec(1), lamhalt(1), lamnodes(1), mpicc(1), mpiCC(1), mpif77(1), mpirun(1), recon(1), tkill(1), tping(1), wipe(1), perror(3) LAM 6.5.8 November, 2002 LAM-HELPFILE(5)
All times are GMT -4. The time now is 10:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy