Features  Scripting SSH Access
SSH Access
 SSH access allows clients to take advantage of easy maintenance of their sites in a LINUX shell. Clients are able to roam through their sites, change permissions, move files, delete files, and debug scripts. Compiling programs or manipulation of MySQL databases is also possible (depending on your hosting plan). SSH is a replacement for the insecure telnet and with tools such as Putty it becomes just as easy to use your shell account as you used to with the old telnet.
Available Shells
Shells are programs (that are not part of the operating system kernel) that allow you to run programs through the command line and see their output. There are different types of shells available to our customers.
Jailed Shell
cPanel's jailed shell came from service providers' desire to establish a clean cut separation between the various services and customers, mainly for security and ease of administration reasons. Instead of adding a new layer of fine-grained configuration options, the solution adopted was to compartmentalize the system, both its files and its resources, in such a way that only the right person(s) are allowed access to the right compartment(s).
Bourne-Again Shell (bash)
The folks from the Free Software Foundation created an exceedingly souped-up version of the so called Bourne shell with automated command completion and plenty of additional functionality. Linux systems typically choose Bash as the "basic" shell used by default. This is by far the most popular shell used by our customers.
Korn shell (ksh)
Korn shell (ksh) written by David Korn, of Bell Labs, is available on virtually any Unix-like system sold in the 1990's and beyond.
It's a reasonable platform for both interactive system control as well as shell script programming, providing far superior functionality to the Bourne Shell. In many cases, it is quite a bit faster, too.
Z Shell (zsh)
Zsh is basically an extended bourne shell with a large number of improvements, including some of the most useful features of bash, ksh, and tcsh.
|
Recent news from comp.security.ssh
-
Re: Chrooted SFTP & logging problems
I tried one of the suggested patches to session.c which allows
arguments to the 'ForceCommand internal-sftp'.
This fixes the problem of getting kicked out of sftp after login then
the 'ForceCommand internal-sftp' has arguments specified. I'm still
not getting the required logging though.
I then tried removing the ChrootDirectory from the Match directive to
-
Re: Chrooted SFTP & logging problems
On Aug 19, 5:39 pm, francois.garillot_NO@SPAM_free .fr (François
Hi - no I don't see the same problem. I've just tried again
commenting out ForceCommand - it works exactly as with it uncommented.
Are you using Solaris? I'm wondering whether I'm encountering issues
with the syslog-ng config (I need to run syslog-ng instead of regular
-
Re: Chrooted SFTP & logging problems
François Garillot asserted on Day 2 of week 34 of 2008: See also the very recent patch proposal for passing arguments to ForceCommand: [link]
-
Re: Chrooted SFTP & logging problems
Rob prated on Sha'ban 10, 1429:
I think I'm running into the same problem. I notice you are using the
ForceCommand directive. For me, suppressing it restores logging, which
would indicate an ssh problem. Is it the same for you ?
Apparently, some people have also encountered this issue with syslogd:
-
Re: Chrooted SFTP & logging problems
I've tried this also creating a second sun-streams source rather than
the unix-stream mentioned above - i.e:
sun-streams("/export/home/myus er/dev/log" door("/export/home/myuser/
var/run/syslog_door"));
I had to create /export/home/myuser/dev/log using mknod (using same
major/minor numbers as the real /dev/log). The door file was created
|
|
HOSTING PLANS
4GB, Mailing Lists, SSH, 3 Domains
More | Order
|
