09-08-2010
chroot issues
hi there people...
i cant seem to get past this "/bin/su : incorrect password" either... ive run the script as prescribed above, but no bananas... im using redhat btw if that counts for anything...and im sure the password is correct..
any help from people who know ??
please.
many thanks
10 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
See:
http://www.cert.org/advisories/CA-2002-36.html
and
http://www.rapid7.com/News/pr021216-ssh.html (1 Reply)
Discussion started by: Neo
1 Replies
2. UNIX for Advanced & Expert Users
I am trying to ssh into a remote sun server, however I get X11 forwarding error. I have checked sshd_config file and X11 forwarding is enabled.
Also xhost command doesnt give any output, it doesnt even return the prompt.I have to Ctrl C out of the situation. any suggestions anyone?? (1 Reply)
Discussion started by: ysk
1 Replies
3. UNIX for Dummies Questions & Answers
I was reading an article on how it is very important to setup a chroot jail to run bind. I can follow what the article says but one thing I am unclear about is now on system boot the BIND process in the chroot jail will start since it the owner will no longer be root but some other user. Can... (1 Reply)
Discussion started by: mojoman
1 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I have a Solaris 10 server with SUN_SSH_1.1 installed.
I want to restrict a user via SFTP to only be able to access one directory. I've written a little script in .profile which works perfectly for an ssh login but it appears sftp doesn't read the .profile file so it doesn't work.
... (2 Replies)
Discussion started by: Donkey25
2 Replies
5. UNIX for Advanced & Expert Users
I have a simple sandbox program which runs a command as user "nobody" in a chroot jail. It sets resource limits with setrlimit, changes the user id with setuid, changes the root dir with chroot, and then calls exec to execute the command given as command line parameters. It is of course a... (8 Replies)
Discussion started by: john.english
8 Replies
6. Solaris
Hello all, does anybody knows a procedure to enable an chroot for users using ssh and sftp ? Thanks (1 Reply)
Discussion started by: celord
1 Replies
7. UNIX for Advanced & Expert Users
I have a developer that needs ssh access to a server to get to a specific directory. I want to restrict them to that directory. I've tried to set their shell as rksh which does jail them but only if they are using ssh from another unix system. If they are using putty or winscp they can still... (2 Replies)
Discussion started by: toor13
2 Replies
8. Red Hat
Hi
I need a specific user to be able to sftp to a server and get files from a specific location. The location is not the users home dir, i don't want the user to be able to view anything else apart from the files in that area.
e.g ftp file are is - /logging/phplogs
e.g user home is... (1 Reply)
Discussion started by: duckeggs01
1 Replies
9. Solaris
I'm attempting to setup RSA Authentication for a particular user on two servers. A script runs via crontab, logs into one server and transfers data from the server1 to server2. Another script via cron, runs on server2, connects to server 1 and transfers data to it. However, I'm having issues... (3 Replies)
Discussion started by: Nvizn
3 Replies
10. UNIX for Beginners Questions & Answers
For some reason, when I try copying my public key to the server, despite it showing as being successful:
rob@linux044:~$ ssh-copy-id -i /home/rob/Work/Keys/keys.txt.pub !@#$%.com
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/rob/Work/Keys/keys.txt.pub"... (7 Replies)
Discussion started by: Circuits
7 Replies
LEARN ABOUT LINUX
vncpasswd
vncpasswd(1) TightVNC vncpasswd(1)
NAME
vncpasswd - set passwords for VNC server
SYNOPSIS
vncpasswd [file]
vncpasswd -t
vncpasswd -f
DESCRIPTION
The vncpasswd utility should be used to create and change passwords for the TightVNC server authentication. Xvnc uses such passwords when
started with the -rfbauth command-line option (or when started from the vncserver script).
vncpasswd allows to enter either one or two passwords. The first password is the primary one, the second password can be used for view-only
authentication. Xvnc will restrict mouse and keyboard input from clients who authenticated with the view-only password. The vncpasswd util-
ity asks interactively if it should set the second password.
The password file name defaults to $HOME/.vnc/passwd unless the -t command-line option was used (see the OPTIONS section below). The
$HOME/.vnc/ directory will be created if it does not exist.
Each password has to be longer than five characters (unless the -f command-line option was used, see its description below). Only the
first eight characters are significant. If the primary password is too short, the program will abort. If the view-only password is too
short, then only the primary password will be saved.
Unless a file name was provided in the command-line explicitly, this utility may perform certain sanity checks to prevent writing a pass-
word file into some hazardous place.
If at least one password was saved successfully, vncpasswd will exit with status code 0. Otherwise the returned status code will be set to
1.
OPTIONS
-t Write passwords into /tmp/$USER-vnc/passwd, creating the /tmp/$USER-vnc/ directory if it does not exist, and checking the permis-
sions on that directory (the mode must be 700). This option can help to improve security when your home partition may be shared via
network (e.g. when using NFS).
-f Filter mode. Read plain-text passwords from stdin, write encrypted versions to stdout. One or two passwords (full-control and view-
only) can be supplied in the input stream, newline terminates a password. Note that in the filter mode, short or even empty pass-
words will be silently accepted.
SEE ALSO
vncserver(1), Xvnc(1), vncviewer(1), vncconnect(1)
AUTHORS
Original VNC was developed in AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people
participated in development, testing and support.
Man page authors:
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>,
Tim Waugh <twaugh@redhat.com>,
Constantin Kaplinsky <const@tightvnc.com>
August 2006 vncpasswd(1)