![]() Resolves: rhbz#1459747 CVE-2017-5664 tomcat: Security constrained bypass in error page mechanism Resolves: rhbz#1495655 CVE-2017-7674 tomcat: Vary header not added by CORS filter leading to cache poisoning Resolves: rhbz#1505762 Problem to start tomcat with a user whose group has a name different to the user Resolves: rhbz#1485453 man page uid and gid mismatch for service accounts Related: rhbz#1505762 Remove erroneous useradd Resolves: rhbz#1602060 Deadlock occurs while sending to a closing session Resolves: rhbz#1608607 CVE-2018-1336 tomcat: A bug in the UTF 8 decoder can lead to DoS Resolves: rhbz#1455483 Add support for characters "" to the possible whitelist values Resolves: rhbz#1472950 shutdown_wait option is not working for Tomcat Resolves: rhbz#1588703 Backport of Negative maxCookieCount value causes exception for Tomcat Resolves: rhbz#1608609 CVE-2018-8034 tomcat: host name verification missing in WebSocket client Resolves: rhbz#1590182 CVE-2018-8014 tomcat: Insecure defaults in CORS filter enable 'supportsCredentials' for all origins Resolves: rhbz#1552374 CVE-2018-1305 tomcat: Late application of security constraints can lead to resource exposure for unauthorised users Resolves: rhbz#1552375 CVE-2018-1304 tomcat: Incorrect handling of empty string URL in security constraints can lead to unintended exposure of resources Resolves: rhbz#1641873 CVE-2018-11784 tomcat: Open redirect in default servlet Resolves: rhbz#1748541 Bump tomcat release number CVE-2020-1938 tomcat: Apache Tomcat AJP File Read/Inclusion Vulnerability Resolves: CVE-2019-17563 tomcat: session fixation when using FORM authentication Resolves: rhbz#1795645 connection leak with StatementCache, SlowQueryReport or StatementDecoratorInterceptor Resolves: rhbz#1822453 Tomcat parses a request having an absolute URI path incorrectly and returns 404 Not Found Resolves: rhbz#1629162 tomcat-dbcp.jar is missing from tomcat package Resolves: rhbz#1523112 tomcat systemd does not cope with - in service names Resolves: rhbz#1367492 harden package permissions ![]() Revert rhbz#1367492 because it caused issues with ipa-server, see rhbz#1831127 Resolves: CVE-2020-9484 tomcat: Apache Tomcat Remote Code Execution via session persistence Revert rhbz#1814315 because it caused other issues with ipa-server, see rhbz#1831127 Resolves: CVE-2020-13935 tomcat: multiple requests with invalid payload length in a WebSocket frame could lead to DoS To be a collaboration of the best-of-breed developers from around the world. Released under the Apache Software License version 2.0. Tomcat is developed in an open and participatory environment and The Java Servlet and JavaServer Pages specifications are developed by Implementation for the Java Servlet and JavaServer Pages technologies. Tomcat is the servlet container that is used in the official Reference Summary: Apache Servlet/JSP Engine, RI for Servlet 3.0/JSP 2.2 API Untar it into GS3/packages and name the folder "tomcat" after moving out the old one.Tomcat-7.0.76-15.el7 RPM for noarch From CentOS for x86_64 Therefore, to try Java 8 with GS3, you will need tomcat 7.0.57. ![]() It seems to be fine, so maybe we can make GS3 ship with the newer tomcat by default, in order for GS3 users to be able to work with Java 8 out of the box. I then repeated the above with the JAVA settings back to JDK 7, to confirm that the newer tomcat works with Java 7. Rebuilding the solr collection from GLI and searching it still works, so on the surface the new tomcat seems to be okay with JDK8. I can search the lucene demo collection after rebuilding it. Restarting the server now allows me to to view the /greenstone3 servlet. The new tomcat contains up-to-date helper jar files for jasper and ecj, as was mentioned at stackoverflow. I extracted it into my new gs3-svn's "package"s folder and renamed the extracted folder to "tomcat", after renaming the old "tomcat" folder there to tomcat-7.0.26. The suggested solution was to update tomcat to 7.0.54. Googling the error led to the stackoverflow page The compilation succeeded but running the GS3 tomcat server initially failed with the error: "The type $Entry cannot be resolved." I then checked out gs3 from SVN and compiled it up. profile and logged out and back in, just to make doubly sure all processes will use this java and no other. I installed JDK1.8, set up the Java environment in my. I worked on an "Ubuntu 14.04 LTS" 64 bit machine (bedrock) here. I can get GS3 to work with Java 8, but only by upgrading the tomcat that GS3 uses to 7.0.57: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |