Uploaded image for project: 'General'
  1. General
  2. GEN-266

Seal as many jars as practical via Maven manifest customization

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved

      Description

      Basic testing suggests that sealing our jars will prevent some, though not by any means all, ways of subverting some of the assumptions we make about loading code, and is good hygiene in general for preventing accidental jar conflicts.

      Notably though, many scenarios do not appear to be impacted by sealing, including the Java Services loader and almost certainly resource loading from the classpath, and those are a somewhat major source of risk themselves.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cantor.2@osu.edu Scott Cantor
              Reporter:
              cantor.2@osu.edu Scott Cantor
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 1 day, 30 minutes
                  1d 30m