alessmicro/passbolt repository overview

PASSBOLT PASSWORD MANAGER⁠

These containers are not to be used in production.They may not work at all. both are rootless containers. they are in alpha stage. the permissions are completely different in rhel container. you might need to rotate your gpg keys and for RHEL specifically

chown -Rf root:nginx /etc/passbolt/jwt/
chmod 750 /etc/passbolt/jwt/
chmod 640 /etc/passbolt/jwt/jwt.key
chmod 640 /etc/passbolt/jwt/jwt.pem

For suse

chown -Rf root:www/etc/passbolt/jwt/
chmod 750 /etc/passbolt/jwt/
chmod 640 /etc/passbolt/jwt/jwt.key
chmod 640 /etc/passbolt/jwt/jwt.pem

You can actually keep the gpg keys also if you can check the permissions and change is as needed also. set the permissions properly. lots of things may not work which is expected behavior as both of them are not standard debian. Ubuntu base and rhel base was changed due to Debian being sometimes slow to roll out standard security fixes. Does not mean debian is not good enough rather ubuntu and rhel has enterprise support so fixes on OS grade CVEs are faster.

Changelog: May 16, 2025: both of our containers now share same High GID, UID of 2000. which means the rootless user UID:GID is same which makes it easier to use both of our containers with RHEL and SUSE base ready to deploy over same set of gpg and jwt volumes but if you used official Passbolt container. The permission UID:GID is different. so you need to run the commands above once only. later if you want to go back to passbolt official container, all you need to do is change the permissions to root:www-data