hello chris,
they only mention on port 8080 and no other info. I will try that telnet
command and see.
On Thu, 6 Aug 2020 at 23:20, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> Fang,
>
> On 8
Hi Chris,
Did that as well, but the scanner still flagged but it is to say is a false
positive result in their scan?
Regards with Thanks,
Fang
On Wed, 5 Aug 2020, 04:21 Christopher Schultz,
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Fang,
>
> On 8/3/
Hello Apache Tomcat,
I have an issue on the subject mentioned as the vulnerability scan flagged
out.
Plugin: 12085
Plugin Text: Apache Tomcat Default Files
Protocol: TCP
Port: 8080
Apache Tomcat 8.5.55 (x64-bit machines)
In my app folder (located in the webapp folder) I already had the necessar
Hi Tomcat,
I would like to know how to encrypt and decrypt the database password in
context.xml when the application is running which also allow me to change
the db password for the purpose of security.
Database driver is Oracle
JDK: 1.8.0_251
Tomcat Version: 8.5.55
Appreciate ya help.
Rgs,
Fa
Hello Martin and John,
Any update on this?
Regards with Thanks,
Fang
On Thu, 4 Jun 2020, 09:48 FANG YAP, wrote:
> Hi Martin,
>
> Thank you for your email.
>
> In my application's web.xml, there is already a default
> error-code that defines 404 (../error_404.jsp)
ot;false"
> to the Error Report Valve section at the bottom of server.xml (and addin or
> or uncommenting that valve section...):
>
> showReport="false" showServerInfo="false" />
>
> On Wed, Jun 3, 2020 at 5:40 AM Martin Grigorov
> wrote:
>
&g
Hello Martin,
It is to say that I have to declare something like this in web.xml file?
java.lang.Exception
/error.jsp
Regards with Thanks,
Fang
On Wed, 3 Jun 2020, 15:56 Martin Grigorov, wrote:
> Hi,
>
> On Wed, Jun 3, 2020 at 5:53 AM FANG YAP wrote:
>
> > Resend
>
Resend
On Wed, 3 Jun 2020, 10:10 FANG YAP, wrote:
> Hi Tomcat,
>
> Nessus scanned and found issue in Apache Tomcat Port 8080
>
> Port: 8080
> Plugin Text:
> The server is not configured to return a custom page in the event of a
> client requesting a non-existent resour
