Sponsored Content
Full Discussion: .bash_history
Top Forums UNIX for Advanced & Expert Users .bash_history Post 28356 by LivinFree on Tuesday 17th of September 2002 12:52:42 PM
Old 09-17-2002
I definitely see your point, but I see a lot of admins who want to "spy" on their users, or a company that does not hire qualified or trustworthy personell. That is where I get my stance.

Being that I am currently working with a company that does demand real-time transactions and reporting 24x7x365, I understand that sometimes "mistakes" are made when trying to quickly solve a production problem, although in a working business they should be minimal.

In my limited experience, I have seen far more cases of hardware failure than "user error". A good case might be a grossly incompetent DBA whose database design is falling in on itself. And if he accidentally drops a critical index on the box, there's a good chance that most people aren't going to see that logged anyways in a typical setting, because many DBAs use tools like SQL Analyzer, or one of the Oracle front-ends... So do you sniff the wire? And where do you store this growing amount of information in a secure manner? Who analyzes it? Is this person authorized to have the various passwords and private information that they are bound to see in these logs? What is the retention policy on it?


I guess I just believe that if you're still trying to figure out how to keep a user from deleting their .bash_history, you probably haven't given this a whole lot of thought or planning in the first place. Nor would you likely have company backing, as this does become a legal privacy issue, if someone is let go for something you saw in this log.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Change .bash_history to another one

we need the help to change .bash_histroy file in root ,(i.e) we want to save the histroy for .temp.txt for permenently. how to do?? Help us (1 Reply)
Discussion started by: thakshina
1 Replies

2. UNIX for Advanced & Expert Users

.bash_history

During the course of the session before I logout I see some of the commands listed from my previous session but not from my current session and after I logout and log back in I see the commands which I ran before logging out. Does the .bash_history stay in the buffer or someplace else then? ... (2 Replies)
Discussion started by: jacki
2 Replies

3. Shell Programming and Scripting

.bash_history

Dear All, I am creating users on our servers. the .bash_history supposed to store all the commands entered by the user. My question is, how can I prevent the user himself from editing or viewing this file? I have tried chaning the owner of the .bash_history to be the root user but... (5 Replies)
Discussion started by: charbel.n.s
5 Replies

4. UNIX for Advanced & Expert Users

.bash_history modification

Hi Experts, I know my question would be strange but i need to understand how the .bash_history file is logging user actions (the mechanism) and if possible modify it to include also the date/time of every action done by the user. Sample file: # more .bash_history ssh <IP address> -l axadmin... (3 Replies)
Discussion started by: Dendany83
3 Replies

5. UNIX for Dummies Questions & Answers

how to store time in .bash_history file

Hi - user commands are written in . bash_history of that user when he logs out. my bash_history file shows. not sure what that number means #1329618972 ls -la #1329618978 ls #1329618980 ls -la my bash_profile looks like this PATH=$PATH:$HOME/bin export PATH export... (3 Replies)
Discussion started by: oraclermanpt
3 Replies

6. UNIX for Advanced & Expert Users

How to recover .bash_history?

rm -rf .bash_history some one ran rm -rf .bash_history on my Linux server(SUSE),I can see this command being run in current history, but I want the OLD history as well,can I recover the old history back. (9 Replies)
Discussion started by: Ankit Bansal
9 Replies

7. Shell Programming and Scripting

Display .bash_history with timestamp using script

Hi would like to ask if there is anyway to display .bash_history with timestamp using shell script? i know that you should use history command with HISTTIMEFORMAT="%d/%m/%y %T " to display it in terminal but it does not work when i use it on shell script. It seem that you can't run history... (1 Reply)
Discussion started by: pikamon
1 Replies

8. UNIX for Beginners Questions & Answers

How to get the "history" command to show all that is in the .bash_history file?

I am using the bash shell. When I view my recent command history using the "history" command from the prompt, it only shows me the commands starting at #928. The commands I need are earlier than that, but I can't figure out how to make the other 927 display. They are in my .bash_history... (1 Reply)
Discussion started by: Twinklefingers
1 Replies
PWGEN(1)						      General Commands Manual							  PWGEN(1)

NAME
pwgen - generate pronounceable passwords SYNOPSIS
pwgen [ OPTION ] [ pw_length ] [ num_pw ] DESCRIPTION
The pwgen program generates passwords which are designed to be easily memorized by humans, while being as secure as possible. Human-memo- rable passwords are never going to be as secure as completely completely random passwords. In particular, passwords generated by pwgen without the -s option should not be used in places where the password could be attacked via an off-line brute-force attack. On the other hand, completely randomly generated passwords have a tendency to be written down, and are subject to being compromised in that fashion. The pwgen program is designed to be used both interactively, and in shell scripts. Hence, its default behavior differs depending on whether the standard output is a tty device or a pipe to another program. Used interactively, pwgen will display a screenful of passwords, allowing the user to pick a single password, and then quickly erase the screen. This prevents someone from being able to "shoulder surf" the user's chosen password. When standard output (stdout) is not a tty, pwgen will only generate one password, as this tends to be much more convenient for shell scripts, and in order to be compatible with previous versions of this program. In addition, for backwards compatibility reasons, when stdout is not a tty and secure password generation mode has not been requested, pwgen will generate less secure passwords, as if the -0A options had been passed to it on the command line. This can be overriden using the -nc options. In the future, the behavior when stdout is a tty may change, so shell scripts using pwgen should explicitly specify the -nc or -0A options. The latter is not recommended for security reasons, since such passwords are far too easy to guess. OPTIONS
-0, --no-numerals Don't include numbers in the generated passwords. -1 Print the generated passwords one per line. -A, --no-capitalize Don't bother to include any capital letters in the generated passwords. -a, --alt-phonics This option doesn't do anything special; it is present only for backwards compatibility. -B, --ambiguous Don't use characters that could be confused by the user when printed, such as 'l' and '1', or '0' or 'O'. This reduces the number of possible passwords significantly, and as such reduces the quality of the passwords. It may be useful for users who have bad vision, but in general use of this option is not recommended. -c, --capitalize Include at least one capital letter in the password. This is the default if the standard output is a tty device. -C Print the generated passwords in columns. This is the default if the standard output is a tty device. -N, --num-passwords=num Generate num passwords. This defaults to a screenful if passwords are printed by columns, and one password. -n, --numerals Include at least one number in the password. This is the default if the standard output is a tty device. -H, --sha1=/path/to/file[#seed] Will use the sha1's hash of given file and the optional seed to create password. It will allow you to compute the same password later, if you remember the file, seed, and pwgen's options used. ie: pwgen -H ~/your_favorite.mp3#your@email.com gives a list of possibles passwords for your pop3 account, and you can ask this list again and again. WARNING: The passwords generated using this option are not very random. If you use this option, make sure the attacker can not obtain a copy of the file. Also, note that the name of the file may be easily available from the ~/.history or ~/.bash_history file. -h, --help Print a help message. -s, --secure Generate completely random, hard-to-memorize passwords. These should only be used for machine passwords, since otherwise it's almost guaranteed that users will simply write the password on a piece of paper taped to the monitor... -v, --no-vowels Generate random passwords that do not contain vowels or numbers that might be mistaken for vowels. It provides less secure pass- words to allow system administrators to not have to worry with random passwords accidentally contain offensive substrings. -y, --symbols Include at least one special character in the password. AUTHOR
This version of pwgen was written by Theodore Ts'o <tytso@alum.mit.edu>. It is modelled after a program originally written by Brandon S. Allbery, and then later extensively modified by Olaf Titz, Jim Lynch, and others. It was rewritten from scratch by Theodore Ts'o because the original program was somewhat of a hack, and thus hard to maintain, and because the licensing status of the program was unclear. SEE ALSO
passwd(1) pwgen version 2.05 January 2006 PWGEN(1)
All times are GMT -4. The time now is 08:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy