Sponsored Content
Special Forums Cybersecurity prevent user from excute command Post 302321767 by otheus on Tuesday 2nd of June 2009 05:35:07 AM
Old 06-02-2009
For such a specific feature, you can set the HISTSIZE variable to 0 and the mark it read-only. Do this in the global initialization (rc) file.

Code:
export HISTSIZE=0
declare -r HISTSIZE

Note, a clever user can still get around this.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can I prevent a user from changing the permissions on their home directory.

Hello All, I have a new HPUX system going into production and it will be used by 2 projects. One of the contract requirements is the 2 groups can not have access to the others work or data. I believe I have the system pretty well locked up using groups and permissions and selective mounting of... (2 Replies)
Discussion started by: DanL
2 Replies

2. UNIX for Advanced & Expert Users

How to prevent local root from su to an NIS user?

We have a shared development box, running Solaris 10 that is an NIS client, all the developers have local root password. If they know the NIS uid of another user, they can just do % useradd -u <uid> login And then log in as that user and have full access to his files in his home directory. ... (3 Replies)
Discussion started by: nfw
3 Replies

3. UNIX for Dummies Questions & Answers

Force user to use ssh/prevent telnet access

I have just set up a user on our system HP-Thru64. The user needs to be able to su to root after they login and this works fine. Users cannot login from root externally so you have to first connect as a user and then su. I am wondering is it possible for me to prevent the user from having telnet... (4 Replies)
Discussion started by: peragin
4 Replies

4. IP Networking

how to prevent a user from downloading on lan

hi all, i want to prevent users downloading files in the office as bandwidth becomes very low and affects work. one of my friend tried to close the connection using ethercap but this does not work. i have a debian desktop while other users use MS W!ndows. Please provide any help. Thanks (5 Replies)
Discussion started by: coolatt
5 Replies

5. UNIX Desktop Questions & Answers

ssh command doesnot excute commands in the destination server

Hi All, I have the below code where Iam connecting from xzur111pap server to xzur0211pap server thru ssh to execute some commands. ssh xzur0211pap spaceleft=`df -k /home |tail -1 | awk '{print $5}'` spaceleft=${spaceleft%\%} if ]; then echo "ALERT : HUFS(/home $spaceleft)" exit 0... (3 Replies)
Discussion started by: gaddamja
3 Replies

6. Shell Programming and Scripting

Login, excute command, logout Script Help

Good Evening all, After spending the last week or so reading many posts I decided to register and join in. This is my first post on the forum so please forgive me as im new to this, Im after some help in throwing together a quick basic script without using expect to change the password on several... (4 Replies)
Discussion started by: mutley2202
4 Replies

7. Shell Programming and Scripting

Prevent the user from changing his directory

Hi could some let me know how to prevent user from changing his home directory....... Thanks in advance.... (1 Reply)
Discussion started by: Revanth547
1 Replies

8. Shell Programming and Scripting

Prevent the user from changing his directory

Hi could some let me know how to prevent user from changing his home directory....... Thanks in advance.... (6 Replies)
Discussion started by: rahul547
6 Replies

9. AIX

Prevent admin user accidentally remove database files.

Hi Folks, Any system admin did provide AIX file system control to prevent user/ admin accidentally remove database files ? Thanks. (4 Replies)
Discussion started by: ckwan
4 Replies

10. UNIX for Advanced & Expert Users

Prevent user from creating new user from his login

Hi Experts, Need your support Redhat 6.5 I want to create a user with all(read, write, execute) privileges except that user should not be able to create any new user from his login to perform any task. (10 Replies)
Discussion started by: as7951
10 Replies
fc(1)							      General Commands Manual							     fc(1)

NAME
fc - Processes the command history list SYNOPSIS
fc [-r] [-e editor] [first[last]] fc -l [-nr] [first[last]] fc [-s] [old=new] [first] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: fc: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Uses the editor named by editor to edit the commands. The editor string is a utility name, subject to search via the PATH variable. The value in the FCEDIT variable is used as a default when -e is not specified. If FCEDIT is null or unset, ed is used as the editor. Lists the commands rather than invoking an editor on them. The commands are written in the sequence indicated by the first and last parameters, as affected by -r, with each command preceded by the command number. Suppresses command numbers when listing with -l. Reverses the order of the commands listed (with -l) or edited (with neither -l nor -s). Reexecutes the command without invoking an editor. OPERANDS
Selects the commands to list or edit. The number of previous commands that can be accessed is determined by the value of the HISTSIZE variable. The value of first or last or both is one of the following: A positive number representing a command number; command numbers can be displayed with the -l option. A negative decimal number representing the command that was executed number of commands previously. For example, -1 is the immediately previous command. A string indicating the most recently entered command that begins with that string. If the old=new operand is not also specified with -s, the string form of the first operand cannot contain an embedded equal sign. When the synopsis form with -s is used: If first is omitted, the previous command is used. For the synopsis forms without -s: If last is omitted, last defaults to the previous command when -l is specified; otherwise, it defaults to first. If first and last are both omitted, the previous 16 commands are listed or the previous single command is edited (based on the -l option). If first and last are both present, all of the commands from first to last are edited (without -l) or listed (with -l). Editing multiple commands is accomplished by presenting to the editor all of the commands at one time, each com- mand starting on a new line. If first represents a newer command than last, the commands are listed or edited in reverse sequence, equivalent to using -r. For example, the following commands on the first line are equivalent to the corresponding commands on the second: fc -r 10 20 fc 30 40 fc 20 10 fc -r 40 30 When a range of commands is used, it is not an error to specify first or last values that are not in the history list; fc substitutes the value representing the oldest or newest command in the list, as appropriate. For example, if there are only ten commands in the history list, numbered 1 to 10, the follow- ing commands list and edit, respectively, all ten commands: fc -l fc 1 99 The first occurrence of string old in the commands to be reexecuted is replaced by the string new. DESCRIPTION
The fc utility lists or edits and reexecutes commands previously entered to an interactive shell. The command history list references commands by number. The first number in the list is selected arbitrarily. The relationship of a num- ber to its command does not change except when the user logs in and no other process is accessing the list, at which time the system may reset the numbering to start the oldest retained command at another number (usually 1). When the number reaches an upper limit, either the value in HISTSIZE or 32767 (whichever is greater), the shell wraps the numbers, starting the next command with number 1. However, despite this optional wrapping of numbers, fc maintains the time-ordering sequence of the commands. For example, if four commands in sequence are given the numbers 32766, 32767, 1 (wrapped), and 2 as they are executed, command 32767 is considered the command previous to 1, even though its number is higher. When commands are edited (when the -l option is not specified), the resulting lines are entered at the end of the history list and then reexecuted by sh. The fc command that caused the editing is not entered into the history list. If the editor returns a non-zero exit sta- tus, this suppresses the entry into the history list and the command reexecution. Any command-line variable assignments or redirection operators used with fc affect both the fc command itself as well as the command that results. The following command reinvokes the previous command, suppressing standard error for both fc and the previous command: fc -s -- -1 2>/dev/null NOTES
Users on windowing systems may want to have separate history files for each window by setting HISTFILE to the following: HIST- FILE=$HOME/.sh_hist$$ RESTRICTIONS
Since editors sometimes use file descriptors as integral parts of their editing, redirecting their file descriptors as part of the fc com- mand can produce unexpected results. For example, if vi is the FCEDIT editor, the following command will not work correctly on many sys- tems: fc -s | more EXIT STATUS
The following exit values are returned: Successful completion of the listing. An error occurred. Otherwise, the exit status is that of the commands executed by fc. ENVIRONMENT VARIABLES
The following environment variables affect the execution of fc: This variable, when expanded by the shell, determines the default value for the -e editor option's editor option-argument. If FCEDIT is null or unset, ed is used as the editor. Determines a path name naming a com- mand history file. If the HISTFILE variable is not set, the shell attempts to access or create a file in your home directory. If the shell cannot obtain both read and write access to, or create, the history file, it uses a default mechanism that allows the history to operate properly. Changes made to HISTFILE after the history file has been initialized are not effective. If more than one instance of the shell is using the same history file, it is unspecified how updates to the history file from those shells interact. As entries are deleted from the history file, they will be deleted oldest first. Determines a decimal number representing the limit to the number of previous commands that are accessible. If this variable is unset, a default of 128 is used. Changes made to HISTSIZE after the history file has been ini- tialized are not effective. Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments and input files). Determines the locale used to affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MES- SAGES. SEE ALSO
Commands: sh(1p) Standards: standards(5) fc(1)
All times are GMT -4. The time now is 09:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy