11-28-2006
Log all connecting users
How can I log all connecting users an log it to a file?
For example:
The user 'megan' login to the machine 'client1' with rlogin.
How and where can I see that she used the rlogin protocol and that her username is megan?
Help..!
/Tonlu
10 More Discussions You Might Find Interesting
1. AIX
How to set a timer for log out users that have been idle for a long time? It is a AIX 5L (0 Replies)
Discussion started by: wtofu
0 Replies
2. UNIX for Dummies Questions & Answers
hi....
how i can configurator a log file on real time....on unix solaris....
thanks a lot....
Best Regards... (3 Replies)
Discussion started by: chanfle
3 Replies
3. UNIX for Dummies Questions & Answers
hi all...
only one question....
what is the file...where show me records login and logout of the unix user's..??
thank you....
I waiting for response... (1 Reply)
Discussion started by: chanfle
1 Replies
4. UNIX for Dummies Questions & Answers
Guys i am new in forum and come to ask some help in this. What i want is to log what users are doing. Someone told me to make a script and get the history commands of all users and storage this in a DB. but the problem in this is, i want to log all things. Why this? why my 2 machines is only a... (4 Replies)
Discussion started by: Amgrim
4 Replies
5. Solaris
Hello,
I'm scurying a server and I'm trying to control what users are using rcp to copy files right now. I've tried to find in last, but it doesn't log there, searched in Sun documentation, so I cannot anywhere telling were rcp stores a log with the users logins. Do you know if is there one and... (1 Reply)
Discussion started by: nefeli
1 Replies
6. UNIX for Advanced & Expert Users
I need to list all the failed log in users as part of audit report. How can I do so in Linux to find all the audit log records and then upload to a table for future reference. I am using oracle 10g on Linux. Hope I will get a quick response from the experts.
Thanks in advance for the tips. (3 Replies)
Discussion started by: oraQ
3 Replies
7. Shell Programming and Scripting
how do i start with this guys?
Sample run:
$ LOGTIME it2015678 <enter>
User it2015678 is CRUZ Tommy H
And has logged on to the system for:
8 hours
12 minutes
from the time this script was run. (1 Reply)
Discussion started by: skypigeon
1 Replies
8. Shell Programming and Scripting
Hi,
please provide the steps/commands to find out the user id list who accessed server before i logon same server.
Thank you very much ffor all your support. (2 Replies)
Discussion started by: sridhardwh
2 Replies
9. Shell Programming and Scripting
I have this task : Check the logintime.txt every minute to only allow user to log in at the specified time.
logintime.txt has the following content: USER TIME_START TIME_STOP
Example:
john 17:00 18:00
My idea is locking the user at the TIME_STOP and unlocking at the TIME_START
while... (4 Replies)
Discussion started by: muffle
4 Replies
10. Ubuntu
I have a user who's having troubles logging into one of my servers, that is authenticating with AD. After glancing over /etc/passwd, I found the users account is different than mine and others who aren't having any issues. What's the difference between these two accounts? What's the "1 60 14 60" ?... (1 Reply)
Discussion started by: Nvizn
1 Replies
LEARN ABOUT OSX
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD