Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Which are root's startup files? Post 302455181 by pinga123 on Tuesday 21st of September 2010 03:42:04 AM
Old 09-21-2010
Which are root's startup files?

I was going through a server hardening manual.
At some interval it was mentioned that there should not be any alias for commands defined in roots startup files .

How would i check it?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Re-initializing startup files without rebooting

Sorry for the newbie question. I'm using OSX BSD by remotely logging in and need to re-initialize the startup sequence but don't want to reboot the machine. How can I do it? Thanks for any help. (3 Replies)
Discussion started by: DrScar
3 Replies

2. UNIX for Dummies Questions & Answers

log files for startup?

log files for startup for AIX is /etc/rc.log.old how about for hpux and solaris? (1 Reply)
Discussion started by: yls177
1 Replies

3. UNIX for Dummies Questions & Answers

Run non-root script as root with non-root environment

All, I want to run a non-root script as the root user with non-root environment variables with crontab. The non-root user would have environment variables for database access such as Oracle or Sybase. The root user does not have the Oracle or Sybase enviroment variables. I thought you could do... (2 Replies)
Discussion started by: bubba112557
2 Replies

4. AIX

Initialization & Startup Files

Hi Every Body, I want to know which files are read by the system during startup (initialization files) & in which order they are read? (2 Replies)
Discussion started by: aldowsary
2 Replies

5. SuSE

Executing set of sh files at system startup

Hi Everybody I am totally new to Linux. We are using Suse Linux version 9. Currently we have 4 to 5 shell scripts which needs to be executed manually by the users.I want these scripts to be run automatically when system starts...something like system startup service. When system is... (1 Reply)
Discussion started by: appleforme1415
1 Replies

6. Shell Programming and Scripting

ubuntu --- code to run python files at startup

hi everyone... we have to run any python file e.g. show.py at startup..i.e. when OS starts it runs automatically. we are proceeding this way, writing a startup script named forfyp2 ,pasting it in init.d , making it exe using chmod , creating startup links using update-rc.d forfyp2 defaults.... (1 Reply)
Discussion started by: sarosh
1 Replies

7. UNIX for Dummies Questions & Answers

Startup Files in Unix

Hi All, Can some one pls explain the order in which the startup files are run? For Bourne shell .profile is run., But what other startup files are present? When is the .aliases file called. (4 Replies)
Discussion started by: gsrikanth99
4 Replies

8. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

9. Shell Programming and Scripting

Apache tomcat startup script not booting at startup.

I copied the script from an AskUbuntu post - #!/bin/bash ### BEGIN INIT INFO # Provides: tomcat7 # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start/Stop Tomcat server ### END INIT INFO ... (14 Replies)
Discussion started by: Hijanoqu
14 Replies
BLHC(1) 						User Contributed Perl Documentation						   BLHC(1)

NAME
blhc - build log hardening check, checks build logs for missing hardening flags SYNOPSIS
blhc [options] <dpkg-buildpackage build log file>.. DESCRIPTION
blhc is a small tool which checks build logs for missing hardening flags. It's licensed under the GPL 3 or later. It's designed to check build logs generated by Debian's dpkg-buildpackage (or tools using dpkg-buildpackage like pbuilder or the official buildd build logs) to help maintainers detect missing hardening flags in their packages. Only gcc is detected as compiler at the moment. If other compilers support hardening flags as well, please report them. If there's no output, no flags are missing and the build log is fine. OPTIONS
--all Force check for all +all (+pie, +bindnow) hardening flags. By default it's auto detected. --arch architecture Set the specific architecture (e.g. amd64, armel, etc.), automatically disables hardening flags not available on this architecture. Is detected automatically if dpkg-buildpackage is used. --bindnow Force check for all +bindnow hardening flags. By default it's auto detected. --buildd Special mode for buildds when automatically parsing log files. The following changes are in effect: o Print tags instead of normal warnings, see "BUILDD TAGS" for a list of possible tags. o Don't check hardening flags in old log files (if dpkg-dev << 1.16.1 is detected). o Don't require Term::ANSIColor. o Return exit code 0, unless there was a error (-I, -W messages don't count as error). --color Use colored (ANSI) output for warning messages. --ignore-arch arch Ignore build logs from architectures matching arch. arch is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-arch-flag arch:flag Like --ignore-flag, but only ignore flag on arch. --ignore-arch-line arch:line Like --ignore-line, but only ignore line on arch. --ignore-flag flag Don't print an error when the specific flag is missing in a compiler line. flag is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-line regex Ignore lines matching the given Perl regex. regex is automatically anchored at the beginning and end of the line to prevent false negatives. NOTE: Not the input lines are checked, but the lines which are displayed in warnings (which have line continuation resolved). Used to prevent false positives. This option can be specified multiple times. --pie Force check for all +pie hardening flags. By default it's auto detected. -h -? --help Print available options. --version Print version number and license. Auto detection for --pie and --bindnow only works if at least one command uses the required hardening flag (e.g. -fPIE). Then it's required for all other commands as well. EXAMPLES
Normal usage, parse a single log file. blhc path/to/log/file If there's no output, no flags are missing and the build log is fine. Parse multiple log files. The exit code is ORed over all files. blhc path/to/directory/with/log/files/* Don't treat missing "-g" as error: blhc --ignore-flag -g path/to/log/file Don't treat missing "-pie" on kfreebsd-amd64 as error: blhc --ignore-arch-flag kfreebsd-amd64:-pie path/to/log/file Ignore lines consisting exactly of "./script gcc file" which would cause a false positive. blhc --ignore-line './script gcc file' path/to/log/file Ignore lines matching "./script gcc file" somewhere in the line. blhc --ignore-line '.*./script gcc file.*' path/to/log/file Use blhc with pbuilder. pbuilder path/to/package.dsc | tee path/log/file blhc path/to/file || echo flags missing BUILDD TAGS
The following tags are used in --buildd mode. In braces the additional data which is displayed. I-hardening-wrapper-used The package uses hardening-wrapper which intercepts calls to gcc and adds hardening flags. The build log doesn't contain any hardening flags and thus can't be checked by blhc. W-compiler-flags-hidden (summary of hidden lines) Build log contains lines which hide the real compiler flags. For example: CC test-a.c CC test-b.c CC test-c.c LD test Most of the time either "export V=1" or "export verbose=1" in debian/rules fixes builds with hidden compiler flags. Sometimes ".SILENT" in a Makefile must be removed. And as last resort the Makefile must be patched to remove the "@"s hiding the real compiler commands. W-dpkg-buildflags-missing (summary of missing flags) CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS missing. I-invalid-cmake-used (version) By default CMake ignores CPPFLAGS thus missing those hardening flags. Debian patched CMake in versions 2.8.7-1 and 2.8.7-2 to respect CPPFLAGS, but this patch was rejected by upstream and later reverted in Debian. Thus those two versions show correct usage of CPPFLAGS even if the package doesn't correctly handle them (for example by passing them to CFLAGS). To prevent false negatives just blacklist those two versions. I-no-compiler-commands No compiler commands were detected. Either the log contains none or they were not correctly detected by blhc (please report the bug in this case). EXIT STATUS
The exit status is a "bit mask", each listed status is ORed when the error condition occurs to get the result. 0 Success. 1 No compiler commands were found. 2 Invalid arguments/options given to blhc. 4 Non verbose build. 8 Missing hardening flags. 16 Hardening wrapper detected, no tests performed. 32 Invalid CMake version used. See I-invalid-cmake-used under "BUILDD TAGS" for a detailed explanation. AUTHOR
Simon Ruderich, <simon@ruderich.org> Thanks to to Bernhard R. Link <brlink@debian.org> and Jaria Alto <jari.aalto@cante.net> for their valuable input and suggestions. COPYRIGHT AND LICENSE
Copyright (C) 2012 by Simon Ruderich This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. SEE ALSO
hardening-check(1), dpkg-buildflags(1) perl v5.14.2 2012-06-27 BLHC(1)
All times are GMT -4. The time now is 03:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy