09-15-2005
Control access, in the sense keep a track of user actions from the time he logs in ... with everything being traced. Also restricting the users in usage od certain commands .. can this be achieved using restricted shell.
thanks for your help
rajesh
9 More Discussions You Might Find Interesting
1. Cybersecurity
Hello All,
Does anyone know of any good utilities for user management/password management for HP-UX? I have 32 switchs (telephone) running HP-UX 10x and managing the users on them is becoming quite time consuming...
Thanks
Brian (1 Reply)
Discussion started by: breigner
1 Replies
2. What is on Your Mind?
I am currently executing a Unix audit & would like some guidance on best practice for the management of root user access.
The organisation is small, with an IT team of approx 25. (6 Replies)
Discussion started by: conaloregan
6 Replies
3. Solaris
I want to know about how to start and kill the process of other unix user. Do I need to change the owner or modify user account itself. ??? (1 Reply)
Discussion started by: vikasdeshmukh
1 Replies
4. UNIX for Dummies Questions & Answers
Does it exist centralized tools on unix for managing users of all servers (like windows AD) ? (1 Reply)
Discussion started by: astjen
1 Replies
5. Solaris
Hi,
Is all of the user account password security settings kept in the /etc/default/passwd file or is there some new control in Solaris 10 that defines these?
I need to know the security settings for passwords in Solaris 10. Also is there any way to find out when accounts were created? ... (3 Replies)
Discussion started by: gwhelan
3 Replies
6. Linux
Hi All,
I have to learn all the user management commend like adduser,useradd,chggrp... etc
I would like to know the syntax or example.
Please give me document or link.
Thanks,
Mani (1 Reply)
Discussion started by: Mani_apr08
1 Replies
7. AIX
Hi
When i search for a user it shows that the user doesn't exist
# lsuser x090817
3004-687 User "x090817" does not exist.
But under /var/spool/mail/ the file named x090817 still exists.
4700 1 -rw-rw---- 1 2090817 mail 603 Apr 12 2010 /var/spool/mail/x090817... (1 Reply)
Discussion started by: aixaixaixaix
1 Replies
8. AIX
We have an environment of around 50 AIX LPARs. We use scripts for user and group account management but it is starting to get unwieldy to document and manage the accounts. It would be doable with scripts but before we dedicate resources to that, I was wondering if there is any product that you... (2 Replies)
Discussion started by: wilford
2 Replies
9. UNIX for Beginners Questions & Answers
Good afternoon all,
Was un-sure on where to post this so I thought I would use this topic...
I was wondering what best practice people use for the deletion of user profiles on AIX systems?
At the moment, I currently don't delete any user profiles, they are just disabled as they... (1 Reply)
Discussion started by: SteveCPayne
1 Replies
LEARN ABOUT XFREE86
git-shell
GIT-SHELL(1) Git Manual GIT-SHELL(1)
NAME
git-shell - Restricted login shell for Git-only SSH access
SYNOPSIS
chsh -s $(command -v git-shell) <user>
git clone <user>@localhost:/path/to/repo.git
ssh <user>@localhost
DESCRIPTION
This is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing
the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the user's home directory.
COMMANDS
git shell accepts the following commands after the -c option:
git receive-pack <argument>, git upload-pack <argument>, git upload-archive <argument>
Call the corresponding server-side command to support the client's git push, git fetch, or git archive --remote request.
cvs server
Imitate a CVS server. See git-cvsserver(1).
If a ~/git-shell-commands directory is present, git shell will also handle other, custom commands by running "git-shell-commands/<command>
<arguments>" from the user's home directory.
INTERACTIVE USE
By default, the commands above can be executed only with the -c option; the shell is not interactive.
If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help command is present
in the git-shell-commands directory, it is run to provide the user with an overview of allowed actions. Then a "git> " prompt is presented
at which one can enter any of the commands from the git-shell-commands directory, or exit to close the connection.
Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or
rename repositories, or change repository descriptions and permissions.
If a no-interactive-login command exists, then it is run and the interactive shell is aborted.
EXAMPLE
To disable interactive logins, displaying a greeting instead:
$ chsh -s /usr/bin/git-shell
$ mkdir $HOME/git-shell-commands
$ cat >$HOME/git-shell-commands/no-interactive-login <<EOF
#!/bin/sh
printf '%s
' "Hi $USER! You've successfully authenticated, but I do not"
printf '%s
' "provide interactive shell access."
exit 128
EOF
$ chmod +x $HOME/git-shell-commands/no-interactive-login
To enable git-cvsserver access (which should generally have the no-interactive-login example above as a prerequisite, as creating the
git-shell-commands directory allows interactive logins):
$ cat >$HOME/git-shell-commands/cvs <<EOF
if ! test $# = 1 && test "$1" = "server"
then
echo >&2 "git-cvsserver only handles "server""
exit 1
fi
exec git cvsserver server
EOF
$ chmod +x $HOME/git-shell-commands/cvs
SEE ALSO
ssh(1), git-daemon(1), contrib/git-shell-commands/README
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-SHELL(1)