Locking down access vi winscp Post: 302958608

Sponsored Content

Operating Systems AIX Locking down access vi winscp Post 302958608 by juredd1 on Friday 23rd of October 2015 06:03:23 PM

10-23-2015

Registered User

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 coming in via winscp and it would appear that winscp does not follow the same rules so the special script not getting invoked and blocking them.
Does users coming in via winscp run the .profile for a given user?

I thought I knew AIX pretty well but this is beyond me at this point.
So users are coming in through winscp and accessing areas that they should not be in. Those areas are more open than they should normally but user when logging in normally don't get shell access they are forced into a program so the areas of concerns were never accessible to them. It's really an application issue that is causing those sensitive areas to be open like they are so they can't be locked down at the file/directory level.

Is anyone aware of a way to lock a user down into their home directory when using tools like winscp? We use chroot type security on our linux "FTP". But not sure how putting chroot type security on this AIX server might affect normal enduser logins to the application that resides on this server as when they come in like they should the application is the one accessing the other sensitive areas and is not allowing the user to access areas that don't belong to them.

Thanks for your time.
Justin

juredd1

View Public Profile for juredd1

Find all posts by juredd1

6 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?

2. AIX

File access issue through sftp/winscp

Hi, I have SSH where I want to restrict browsing for a user "drrep" to the assigned home directory only.So I have put a entry in the sshd_config file as �AllowFiles "drrep:/fcrarch/fl02r/*" as shown in the scrren below. But due to this setting none of the users are able to login through winscp...

3. 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..

4. AIX

WINSCP Log in AIX 6.1

Hello Team, In my environment , Application team using winscp to create/modify/delete the files in the AIX server from their windows boxes. I have enabled the user history, su logs and lastlog, but the users whoever using winscp its not getting tracked. How to enable the WINSCP logs in AIX...

5. 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?

6. UNIX for Dummies Questions & Answers

Putty and winscp - what is the difference?

Want to understand the difference between putty and winscp. thanks in advance

LEARN ABOUT DEBIAN

git-annex-shell

git-annex-shell(1)					      General Commands Manual						git-annex-shell(1)

NAME

       git-annex-shell - Restricted login shell for git-annex only SSH access

SYNOPSIS

       git-annex-shell [-c] command [params ...]

DESCRIPTION

       git-annex-shell is a restricted shell, similar to git-shell, which can be used as a login shell for SSH accounts.

       Since  its  syntax  is  identical to git-shell's, it can be used as a drop-in replacement anywhere git-shell is used. For example it can be
       used as a user's restricted login shell.

COMMANDS

       Any command not listed below is passed through to git-shell.

       Note that the directory parameter should be an absolute path, otherwise it is assumed to be relative to the user's home directory. Also the
       first "/~/" or "/~user/" is expanded to the specified home directory.

       configlist directory
	      This outputs a subset of the git configuration, in the same form as git config --list

       inannex directory [key ...]
	      This checks if all specified keys are present in the annex, and exits zero if so.

       dropkey directory [key ...]
	      This drops the annexed data for the specified keys.

       recvkey directory key
	      This runs rsync in server mode to receive the content of a key, and stores the content in the annex.

       sendkey directory key
	      This runs rsync in server mode to transfer out the content of a key.

       commit directory
	      This commits any staged changes to the git-annex branch.	It also runs the annex-content hook.

OPTIONS

       Most options are the same as in git-annex. The ones specific to git-annex-shell are:

       --uuid=UUID
	      git-annex uses this to specify the UUID of the repository it was expecting git-annex-shell to access, as a sanity check.

HOOK

       After  content is received or dropped from the repository by git-annex-shell, it runs a hook, .git/hooks/annex-content (or hooks/annex-con-
       tent on a bare repository). The hook is not currently passed any information about what changed.

ENVIRONMENT

       GIT_ANNEX_SHELL_READONLY

	      If set, disallows any command that could modify the repository.

       GIT_ANNEX_SHELL_LIMITED
	      If set, disallows running git-shell to handle unknown commands.

SEE ALSO

       git-annex(1)

       git-shell(1)

AUTHOR

       Joey Hess <joey@kitenet.net>

       <http://git-annex.branchable.com/>

																git-annex-shell(1)