Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29071

Jenkins not following symlink of archived directory since upgrade to 1.615

    Details

    • Similar Issues:

      Description

      In my environment, to save disk space, I move a directory that is an archive onto another file server and create a symlink pointing to this location. This was working fine using version 1.594.

      I just upgraded from 1.594 to 1.615

      After the upgrade, I noticed those links are not accessible anymore in Jenkins, even though they exist on the file system.

      See attached screenshot.

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          Please attach screenshots as images.

          Show
          danielbeck Daniel Beck added a comment - Please attach screenshots as images.
          Hide
          danielbeck Daniel Beck added a comment -

          This is by design, Jenkins does not follow symlinks that escape the base directory of whatever you're viewing as a security measure (SECURITY-162 in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27).

          Show
          danielbeck Daniel Beck added a comment - This is by design, Jenkins does not follow symlinks that escape the base directory of whatever you're viewing as a security measure (SECURITY-162 in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 ).

            People

            • Assignee:
              Unassigned
              Reporter:
              jaystan Jason Stanley
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: