Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Generating SSL certificate for Apache HTTPD breaks SSH

Subject: Re: Generating SSL certificate for Apache HTTPD breaks SSH
Date: Fri, 8 Dec 2006 11:53:41 -0600 (CST)
On Thu, 7 Dec 2006, samljones wrote:

I have apache web server and SSH installed on a server. I have generated a
SSL certificate for the web server 
http://slacksite.com/apache/certificate.html
http://slacksite.com/apache/certificate.html . When I install the
certificate, though, SSH stops accepting incoming connections. Any existing
connections continue unmolested, but new connections are not accepted until
I reboot the server; luckily, the certificate forces apache to require a
manual start, so it's not running (and blocking SSH) after a reboot.

That webpage above teaches how "to remove the pass-phrase from the key".

Are you saying that you can ssh in fine until apache is started?

sjones[~]$ slogin -v -l gladmin camdevnet02
OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
...

gladmin@camdevnet02's password: 
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
===========================================

After that last line, the cursor goes to the next line, and hangs. No
connection, no rejection, no command line, just flashing cursor. Can't even
ctrl-c out of it; have to close the terminal/tab.

How do you know there is no connection? Maybe there is a connection, but 
no interactive shell (or shell is hanging)?

On Thu, 7 Dec 2006, samljones wrote:

Further information:

Restarting SSHD gives no change. Also, SCP transfers are not blocked or
hindered in any way by this.

Maybe there is something wrong with your login shell or dot files used by 
your login shell.

<Prev in Thread] Current Thread [Next in Thread>