Thanks for reply,
Hi Peter - it complains on port 8443 which belongs to Tomcat.
Hi Mark - Yes. making HTTP request on HTTPS is wrong. But this security
vulnerability is given to us by Qualys scan. It tries to post plain HTTP
request on HTTPS port and then gets error message "Bad Request. This
On 25/08/2020 16:40, ratatouille wrote:
> Mark Thomas schrieb am 25.08.20 um 11:31:59 Uhr:
>
>> On 25/08/2020 11:07, ratatouille wrote:
>
>>> I am running openmeetings on a CentOS 8 server and start it with startup.sh
>>> in the bin-folder.
>>>
>>> The problem is when I execute shutdown.sh the
The only time I ran into this is when I had conflict on the shutdown
port or multiple instances which had a port conflict on the shutdown
port. Other than that, I don't know. Possible permissions issues?
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified
I think I found something.
At the very bottom of LE's FAQ page, https://letsencrypt.org/docs/faq
(under "I successfully renewed a certificate but validation . . ."), I
found:
Once you successfully complete the challenges for a domain, the
resulting authorization is cached for your account to
Mark Thomas schrieb am 25.08.20 um 11:31:59 Uhr:
> On 25/08/2020 11:07, ratatouille wrote:
> > I am running openmeetings on a CentOS 8 server and start it with startup.sh
> > in the bin-folder.
> >
> > The problem is when I execute shutdown.sh the process still exists after.
> > I have to kill
On Tue, Aug 25, 2020 at 8:29 AM Mark Thomas wrote:
>> Enhancement requests for this should go to Commons Daemon. Should
> >> be simple enough just to dump current config.
> >
> > Done.
> >
> > https://issues.apache.org/jira/browse/DAEMON-422
>
> Done.
>
> It outputs the command to (re-)create the
I had to write some custom code to look for the lets encrypt headers
then respond appropriately for verification. It wasn't too bad,
although I don't like having that entity-specific code in there so
I've isolated and commented it.
On 8/25/20, Christopher Schultz wrote:
> -BEGIN PGP SIGNED
On 04/08/2020 14:47, Christopher Schultz wrote:
>> Enhancement requests for this should go to Commons Daemon. Should
>> be simple enough just to dump current config.
>
> Done.
>
> https://issues.apache.org/jira/browse/DAEMON-422
Done.
It outputs the command to (re-)create the current config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 8/24/20 13:24, James H. H. Lampert wrote:
> On 8/24/20 9:57 AM, Christopher Schultz wrote:
>> So your RewriteCond[ition] is expected to always be true? Okay.
>> Maybe remove it, then? BTW I think your rewrite will strip query
>> strings
I'd like to propose some changes to the docs, but can not locate their
source to submit a request.
For instance, in https://tomcat.apache.org/tomcat-9.0-doc/config/host.html
"If the name takes the form of |*.domainname| (e.g. |*.apache.org|) then
it will be treated as a match for any host in
On 25/08/2020 11:14, Pratik Shrestha wrote:
> Hi all,
>
> Tomcat version: 9.0.37
>
> Our website is running on Tomcat. We did Qualys vulnerability scan on our
> site. Scan shows below vulnerability.
>
> Insecure transport
> Group: Information Disclosure
> CWE CWE-319
> OWASP A3 Sensitive Data
On 25/08/2020 11:07, ratatouille wrote:
> Hello!
>
> I am running openmeetings on a CentOS 8 server and start it with startup.sh
> in the bin-folder.
>
> The problem is when I execute shutdown.sh the process still exists after.
> I have to kill it manually.
>
> #
>
Pratik,
> Am 25.08.2020 um 12:14 schrieb Pratik Shrestha :
>
> Hi all,
>
> Tomcat version: 9.0.37
>
> Our website is running on Tomcat. We did Qualys vulnerability scan on our
> site. Scan shows below vulnerability.
>
> Insecure transport
> Group: Information Disclosure
> CWE CWE-319
> OWASP
Hi all,
Tomcat version: 9.0.37
Our website is running on Tomcat. We did Qualys vulnerability scan on our
site. Scan shows below vulnerability.
Insecure transport
Group: Information Disclosure
CWE CWE-319
OWASP A3 Sensitive Data Exposure
WASC WASC-4 INSUFFICIENT TRANSPORT LAYER PROTECTION
Hello!
I am running openmeetings on a CentOS 8 server and start it with startup.sh
in the bin-folder.
The problem is when I execute shutdown.sh the process still exists after.
I have to kill it manually.
# -
# Stop
On 25/08/2020 09:19, Mark Thomas wrote:
> On 24/08/2020 15:41, Aryeh Friedman wrote:
>
>
>
>> Tried and it gives me /usr/local/apache-tomcat-9.0/webapps as the effective
>> dir. This is *NOT* what I meant by the root dir I meant the one that is
>> the highest point in the file system
Am 24.08.20 um 16:41 schrieb Aryeh Friedman:
> On Mon, Aug 24, 2020 at 4:27 AM Mark Thomas wrote:
>
>> On 23/08/2020 22:05, Aryeh Friedman wrote:
>>> In order to allow my developers to quickly access any temporarily
>> produced
>>> html files created/stored outside of webapps (such as those
On 24/08/2020 15:41, Aryeh Friedman wrote:
> Tried and it gives me /usr/local/apache-tomcat-9.0/webapps as the effective
> dir. This is *NOT* what I meant by the root dir I meant the one that is
> the highest point in the file system hierarchy (i.e. the one you get when
> at a shell prompt
18 matches
Mail list logo
