[
https://issues.apache.org/jira/browse/KNOX-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Chen updated KNOX-2469:
-----------------------------
Attachment: 0001-Fixing-Knox-symlink.patch
Status: Patch Available (was: Open)
I have a patch here to directly address the issue, but it's worth noting that
this still breaks if there is a symlink in the directory ancestry that's not
defined–for example, if C:\a\b were a symlink to C:\z, but C:\z is not created,
then a check for C:\a\b\c would fail on the directory creation step. Trying to
fix this would complicate the logic a bit though–would this be best left to the
users?
> Knox keystore directory creation fails when following a symlink
> ---------------------------------------------------------------
>
> Key: KNOX-2469
> URL: https://issues.apache.org/jira/browse/KNOX-2469
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.4.0, 1.5.0
> Reporter: James Chen
> Priority: Minor
> Labels: easy-fix, patch-available
> Fix For: 1.5.0, 1.4.0
>
> Attachments: 0001-Fixing-Knox-symlink.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> At the moment, if the keystore path does not exist, Knox attempts to create
> the parent directories of the keystore path recursively. However, there is an
> edge case, as described in JDK-8130464, where the directory creation fails if
> the final, parent directory of the keystore path is a symlink. This causes a
> failure during startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
