mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 09:26:00 +03:00
[GH-ISSUE #3878] Permission error on a not related certificate when migrating from 2.6.2 to 2.6.3 #1925
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1925
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @olaf7 on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/3878
I am upgrading Modoboa 2.6.0 to 2.6.5 on Debian Trixie with a virtual environment. It is a manual installation.
Upgrading went fine until 2.6.2
When upgrading to 2.6.3 the command
Gave a permission error:
Modoboa should stay away from files which it has no relevance on.
My Modoboa server runs on a server with other software installed on it as well. This interaction is not desired. The subdomain in the certificate name is not registered with Modoboa, nor the file is.
@tonioo commented on GitHub (Jan 13, 2026):
@olaf7 This error is not raised by Modoboa but by a dependency => niquests and wassima.
Wassima is a package to access local certificates store, and it is probably used by niquests to do certificate validation and verification.
I'm pretty sure you should allow read access on certificates that are located in your server store.
@olaf7 commented on GitHub (Jan 13, 2026):
We can have a debate on security (settings) and requirements of various software components and the complications that get introduced by them, Regardless the issue remains a file gets accessed which should not have been accessed as it has nothing to do with Modoboa, This prevents a successful migration. Changing permissions in a more or less secure way will be a struggle as I experienced before. This should not be needed when only relevant files would be accessed.
How can we fix this without making all certificates world readable?
@tonioo commented on GitHub (Jan 14, 2026):
Here is function generating this issue: https://github.com/jawah/wassima/blob/main/src/wassima/init.py#L54.
I'm afraid there no other way to fix this one than replacing the dependency and honestly, good luck to find one that is maintained.
Anyway, I don't see why it is a security issue to make public certificates readable by everyone...
@olaf7 commented on GitHub (Jan 19, 2026):
Thank you. After checking the code I see it recursively links PEM certs. Why this is needed for Modoboa is not clear to me. I still think software should not try to handle files it does not need. The library does also a bad job, by reporting a permission error on, in my case, a dangling symlink.
I fixed my instance and are no longer bothered by this error. And as it is a third party library and not part of Modoboa I suggest to close this issue.