summaryrefslogtreecommitdiffhomepage
path: root/docs/changes.xml
diff options
context:
space:
mode:
authorValentin Bartenev <vbart@nginx.com>2021-03-15 14:57:31 +0300
committerValentin Bartenev <vbart@nginx.com>2021-03-15 14:57:31 +0300
commitb0a1266835386590c65ec433759c5cc1063bd472 (patch)
tree2047a7d17e9849b44eeb2364bdb8d7b95525698a /docs/changes.xml
parenta1107e859b5f401261d378fc251667bcf2272536 (diff)
downloadunit-b0a1266835386590c65ec433759c5cc1063bd472.tar.gz
unit-b0a1266835386590c65ec433759c5cc1063bd472.tar.bz2
Fixed certificates loading on startup with some filesystems.
It appears that readdir() on Linux detects file types unreliably, always setting the "d_type" field to DT_UNKNOWN for some less common filesystems. As a result, all files were skipped and no certificate bundles were found when the state directory was located on such filesystems. Skipping "." and ".." instead of any non-regular files should be enough, as no other non-regular files normally appear in this directory. This closes #368 issue on GitHub.
Diffstat (limited to '')
-rw-r--r--docs/changes.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/changes.xml b/docs/changes.xml
index d9d25e5c..07decb2a 100644
--- a/docs/changes.xml
+++ b/docs/changes.xml
@@ -30,6 +30,13 @@ reconfiguring an application; the bug had appeared in 1.19.0.
</para>
</change>
+<change type="bugfix">
+<para>
+persistent storage of certificates might've not worked with some filesystems in
+Linux, and all uploaded certificate bundles were forgotten after restart.
+</para>
+</change>
+
</changes>