Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyStoreScanner is not able to monitor a symlink file and always resolves to the target. #8786

Closed
lachlan-roberts opened this issue Oct 31, 2022 · 5 comments · Fixed by #8787
Assignees
Labels
Bug For general bugs on Jetty side

Comments

@lachlan-roberts
Copy link
Contributor

Jetty version(s)
9.4.x, 10.0.x, 11.0.x

Description
KeyStoreScanner is not able to monitor a symlink file and always resolves to the target.

There is a test org.eclipse.jetty.test.KeyStoreScannerTest#testReloadChangingSymbolicLink which is incorrectly testing that this use case works, but it is currently not possible to configure in KeyStoreScanner.

@sbordet
Copy link
Contributor

sbordet commented Nov 1, 2022

I miss why do we want to monitor the symlink, seems to make no sense to me?

@joakime
Copy link
Contributor

joakime commented Nov 1, 2022

The symlink can be changed to point to a different location?
The underlying filesystem mounts can change, making what the symlink is pointing to different? (or even invalid)

@joakime
Copy link
Contributor

joakime commented Nov 1, 2022

@lachlan-roberts don't forget to set labels and projects.

@lachlan-roberts
Copy link
Contributor Author

A user was requesting this feature, they wanted to modify the symlink file to point to a new target instead of just changing the target file of the symlink.

We had a test for it which was wrong. So very least we should fix the test to verify the behaviour we expect.

@joakime joakime moved this from To do to 🔖 Review in progress in Jetty 10.0.13 / 11.0.13 - FROZEN Nov 9, 2022
@joakime joakime moved this from 🔖 Review in progress to To do in Jetty 10.0.13 / 11.0.13 - FROZEN Nov 9, 2022
Repository owner moved this from To do to ✅ Done in Jetty 10.0.13 / 11.0.13 - FROZEN Nov 10, 2022
lachlan-roberts added a commit that referenced this issue Nov 10, 2022
…er-Symlink

Issue #8786 - add configuration for KeyStoreScanner to not resolve aliases
joakime added a commit that referenced this issue Dec 6, 2022
…nges

+ Removed changes from #8786 and #8787
+ More test cases

Signed-off-by: Joakim Erdfelt <[email protected]>
joakime added a commit that referenced this issue Dec 7, 2022
…nges (#9014)

* Issue #8973 - Rework KeyStoreScanner handling for symlink related changes

+ Removed changes from #8786 and #8787
+ More test cases
+ revert jetty.sslContext.reload.followLinks boolean
+ Scanner should follow its own linkOptions setting
+ remove bad documentation in module-ssl-reload.adoc

Signed-off-by: Joakim Erdfelt <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Co-authored-by: Lachlan Roberts <[email protected]>
@joakime
Copy link
Contributor

joakime commented Dec 7, 2022

This feature has been further updated as part of PR #9014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants