On Fri, Nov 15, 2013 at 05:58:27PM +, Schuster, David wrote:
> Nessus – is what we are using. I found an article that if you telnet to 8005
> and type SHUTDOWN – it will stop tomcat, which it did. I have modified that
> so hopefully that will fix my problem.
Ah, so it's not just a port sca
cal Support
>
> PO Box 425528
>
> Denton TX 76204-5528
>
>
>
> Phone: 940-898-3909
>
> Fax: 940-898-3764
>
>
>
> dschus...@twu.edu
>
>
>
> *From:* Hilton Gibson [mailto:hilton.gib...@gmail.com]
> *Sent:* Friday, November 15, 2013 9:17 AM
> *To:
pace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Problem with Debian and DSpace during port scan
Hi David
What application do you use for the port scan?
Also what version of DSpace and what server operating system?
Cheers
hg
On 15 November 2013 16:48, Schuster, David
mailto:dschus...@mail.twu.edu>&
Hi, David, I'm not a security expert, but it sounds to me like your port
scanner hit the Tomcat shutdown port. Here's an article on hardening
Apache Tomcat:
http://www.mulesoft.com/improving-apache-tomcat-security-step-step-guide
It's perfectly fine to set the Tomcat shutdown port to -1, which d
Hi David
What application do you use for the port scan?
Also what version of DSpace and what server operating system?
Cheers
hg
On 15 November 2013 16:48, Schuster, David wrote:
> This may not be a Dspace issue, but hopefully someone can point me in
> the right direction. During a port sca
This may not be a Dspace issue, but hopefully someone can point me in the right
direction. During a port scan of our Dspace instance before we make it public
Apache/Tomcat shutsdown.
Being fairly new to tomcat - where might I look and in which log to determine
why this is happening? I am open
6 matches
Mail list logo
