ssh issue

hi,

after the upgrade of our box(remote location and no other user
available to fix the problem), our default shell BASH has corrupted
and I cannot logon using ssh.

I remember back in the days, my friends showed me the trick of using
ssh command option to choose different login shell(tcsh,ksh,sh,
whatever is available)...

Does anyone know how?

ssh -version
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
Bad escape character 'rsion'.

Thanks in advance....

ssh -?
ssh: illegal option -- ?
Usage: ssh [options] host [command]
Options:
-l user Log in using this user name.
-n Redirect input from /dev/null.
-F config Config file (default: ~/.ssh/config).
-A Enable authentication agent forwarding.
-a Disable authentication agent forwarding (default).
-X Enable X11 connection forwarding.
-x Disable X11 connection forwarding (default).
-i file Identity for public key authentication (default:
~/.ssh/identity)
-t Tty; allocate a tty even if command is given.
-T Do not allocate a tty.
-v Verbose; display verbose debugging messages.
Multiple -v increases verbosity.
-V Display version number only.
-q Quiet; don't display any warning messages.
-f Fork into background after authentication.
-e char Set escape character; ``none'' = disable (default: ~).
-c cipher Select encryption algorithm
-m macs Specify MAC algorithms for protocol version 2.
-p port Connect to this port. Server must be on the same port.
-L listen-port:hostort Forward local port to remote address
-R listen-port:hostort Forward remote port to local address
These cause ssh to listen for connections on a port, and
forward them to the other side by connecting to
hostort.
-D port Enable dynamic application-level port forwarding.
-C Enable compression.
-N Do not execute a shell or command.
-g Allow remote hosts to connect to forwarded ports.
-1 Force protocol version 1.
-2 Force protocol version 2.
-4 Use IPv4 only.
-6 Use IPv6 only.
-o 'option' Process the option as if it was read from a
configuration file.
-s Invoke command (mandatory) as SSH2 subsystem.
-b addr Local IP address.

(E-Mail Removed) wrote:
> after the upgrade of our box(remote location and no other user
> available to fix the problem), our default shell BASH has corrupted
> and I cannot logon using ssh.

> I remember back in the days, my friends showed me the trick of using
> ssh command option to choose different login shell(tcsh,ksh,sh,
> whatever is available)...

> Does anyone know how?

ssh foo@remote_mach /bin/tcsh

Peter

On Thu, 23 Sep 2004 06:11:33 +0200, P.T. Breuer <(E-Mail Removed)> wrote:
| (E-Mail Removed) wrote:
|> after the upgrade of our box(remote location and no other user
|> available to fix the problem), our default shell BASH has corrupted
|> and I cannot logon using ssh.
|
|> I remember back in the days, my friends showed me the trick of using
|> ssh command option to choose different login shell(tcsh,ksh,sh,
|> whatever is available)...
|
|> Does anyone know how?
|
| ssh foo@remote_mach /bin/tcsh


If the corruption is more extensive, and some libraries are missing,
then /bin/sash may be a better choice, assuming it is installed.

This is a Stand Alone (or System Admin) shell that has cut-down versions
of some usefull commands built in, so they will work without libraries.


--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/~paulcol
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro