Sponsored Content
Full Discussion: WINSCP Log in AIX 6.1
Operating Systems AIX WINSCP Log in AIX 6.1 Post 302645391 by dunkar70 on Wednesday 23rd of May 2012 10:19:10 AM
Old 05-23-2012
I cannot speak to AIX; however, WinSCP is a client tool I have used to access Solaris and Linux systems. You can have users enable activity logging in WinSCP, but you cannot enforce it without setting up group policies. To my knowledge you cannot execute the SU command in the GUI, but you can in the terminal (either the built-in or by linking to PuTTY).

So... question for you... are your users using their own credentials to access the server, then using SU through the terminal session to get elevated priviledges? If so, then your logging should catch their activity. Alternately, are the users using the elevated accounts (i.e. root) in the GUI to access the server directly? If so, you will not see who is using the root account, only that the root account took some action.

One way to overcome this is to remove login capability from all elevated accounts and force users to login with their own accounts, then SU to the elevated accounts. Many admins would consider this a safer approach anyway.
 

5 More Discussions You Might Find Interesting

1. Linux

WINSCP for Linux?

Is there something that will work on Linux with the same functionality like Winscp? (5 Replies)
Discussion started by: soupbone38
5 Replies

2. AIX

winscp between AIX and windows

Hello Admins, I am trying to copy some files/packages from my windows host to AIX server. I am a normal user not root. I am getting an error as below: cannot initialize sftp protocol..... I have enabled the ftp service. Could you help me out.. (7 Replies)
Discussion started by: snchaudhari2
7 Replies

3. UNIX for Dummies Questions & Answers

Oracle client install for AIX - WinSCP fails

I am trying to install the oracle client for AIX. I downloaded the client to my Windows machine from Oracle Database 10g Release 2 for AIX5L "Oracle Database 10g Client Release 2 (10.2.0.1.0)". 1. Is this right? (I need 9 or 10 client) It was .gz file that I am now trying to move from... (2 Replies)
Discussion started by: shoefiend
2 Replies

4. UNIX for Dummies Questions & Answers

What is winscp?

Hi I am new to using unix and editors for unix.. what is winscp? how to use it? what are ways to download this and learn? (1 Reply)
Discussion started by: swathi123
1 Replies

5. AIX

Locking down access vi winscp

Did some search but didn't find what I was looking for. We have a fairly complex system in which we have a special shell that is actually a script that runs some checks to make sure the user is coming in via the approved ssh client and if not they are kicked out. Recently we figured out folks are... (3 Replies)
Discussion started by: juredd1
3 Replies
HOSTS.EQUIV(5)						     Linux Programmer's Manual						    HOSTS.EQUIV(5)

NAME
hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system DESCRIPTION
The file /etc/hosts.equiv allows or denies hosts and users to use the r-commands (e.g., rlogin, rsh, or rcp) without supplying a password. The file uses the following format: +|[-]hostname|+@netgroup|-@netgroup [+|[-]username|+@netgroup|-@netgroup] The hostname is the name of a host which is logically equivalent to the local host. Users logged into that host are allowed to access like-named user accounts on the local host without supplying a password. The hostname may be (optionally) preceded by a plus (+) sign. If the plus sign is used alone, it allows any host to access your system. You can explicitly deny access to a host by preceding the hostname by a minus (-) sign. Users from that host must always supply additional credentials, including possibly a password. For security reasons you should always use the FQDN of the hostname and not the short hostname. The username entry grants a specific user access to all user accounts (except root) without supplying a password. That means the user is NOT restricted to like-named accounts. The username may be (optionally) preceded by a plus (+) sign. You can also explicitly deny access to a specific user by preceding the username with a minus (-) sign. This says that the user is not trusted no matter what other entries for that host exist. Netgroups can be specified by preceding the netgroup by an @ sign. Be extremely careful when using the plus (+) sign. A simple typographical error could result in a standalone plus sign. A standalone plus sign is a wildcard character that means "any host"! FILES
/etc/hosts.equiv NOTES
Some systems will honor the contents of this file only when it has owner root and no write permission for anybody else. Some exceptionally paranoid systems even require that there be no other hard links to the file. Modern systems use the Pluggable Authentication Modules library (PAM). With PAM a standalone plus sign is considered a wildcard character which means "any host" only when the word promiscuous is added to the auth component line in your PAM file for the particular service (e.g., rlogin). EXAMPLE
Below are some example /etc/host.equiv or ~/.rhosts files. Allow any user to log in from any host: + Allow any user from host with a matching local account to log in: host Note: the use of +host is never a valid syntax, including attempting to specify that any user from the host is allowed. Allow any user from host to log in: host + Note: this is distinct from the previous example since it does not require a matching local account. Allow user from host to log in as any non-root user: host user Allow all users with matching local accounts from host to log in except for baduser: host -baduser host Deny all users from host: -host Note: the use of -host -user is never a valid syntax, including attempting to specify that a particular user from the host is not trusted. Allow all users with matching local accounts on all hosts in a netgroup: +@netgroup Disallow all users on all hosts in a netgroup: -@netgroup Allow all users in a netgroup to log in from host as any non-root user: host +@netgroup Allow all users with matching local accounts on all hosts in a netgroup except baduser: +@netgroup -baduser +@netgroup Note: the deny statements must always precede the allow statements because the file is processed sequentially until the first matching rule is found. SEE ALSO
rhosts(5), rlogind(8), rshd(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-07-23 HOSTS.EQUIV(5)
All times are GMT -4. The time now is 12:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy