Psi Probe 3.0.0.RC1 Released

234 views
Skip to first unread message

Jeremy Landis

unread,
Dec 15, 2016, 5:36:00 PM12/15/16
to psi-probe
After much delay we are offiicially at a release candidate stage for 3.0.0.  Please read release notes here as well as find the download -> https://github.com/psi-probe/psi-probe/releases/tag/3.0.0.RC1

Latest sonatype snapshot has also been updated and can be found here -> https://oss.sonatype.org/content/repositories/snapshots/com/github/psi-probe/

Supported

  • Supports tomcat 7.0.15+, 8 (any), 8.5 (any), and 9 (any)
  • Based on Spring 4.3 and Spring Security 4.2
  • Using 'hazendaz' fork of displaytag (maintenance mode)
  • Vulnerability Free libraries used

New Features

  • Supports copying single file into deployed context
  • Log display for Slf4j requires 1.7.21+, error will be noted in logs but other logs will display. Due to breaking change in slf4j library that couldn't be avoided.
  • Better logging around secure functions
  • Added dbcp2 support
  • SingleThreadModel supported on both older tomcat releases and latest
  • Silk images are all now PNG now. This covers quite a few images but we still have considerable gif images.
  • Utf-8 used by default throughout code where not otherwise previously defined

Breaking Change

  • Users using '/logs/index.htm' will need to use either '/logs' or '/logs/list.htm'

Corrections

  • Corrected session expiry link
  • Corrected problems with images that reached 2.4.0.SP1 but was missed on prior 3.0.0.M3
  • Removed tomcat 5.5 mentions
  • More complete language support
  • Prevention of unexpected session creation
  • Quartz jobs now listed as psi probe
  • Security enhancements, stack trace will no longer be shown on webpage but rather in logs only
  • Some XSS corrections
  • Removed legacy java 1.4 checks
  • File are all closed after usage now
  • And lots and lots of TLC on codebase

Known Possible Issues

  • Spring 4.3 resulted in a number of 405/POST errors. If any 405 / POST errors found still in codebase, please report as we have a fix but couldn't confirm everywhere it was needed.

Reply all
Reply to author
Forward
0 new messages