@jodumont said in Harden security features: provide and identifiy authentification via SAML (if it is possible) SAML is an old and outdated protocol (that is also hard to work with), a more modern alternative is oidc (OpenID Connect, a standard based on Oauth 2.0), which is also offered in your screenshot.

@mehdi said in Disk IO Tracker: just trying to periodically write stuff and checking the performance, as suggested, would not be great IMO, as it would 1/ be influenced by what's already running on the system 2/ wear out SSDs for little benefit Agreed, there are better ways, the example was more for the output or datapoints. Aspects of BPF tools make this light on resources, but there's a whole stack of tools down the line, including 'iolatency'.

@jodumont I recently posted about crowdsec under feature requests. I think crowdsec is more appropriate, afaik, for cloudron

@nebulon Great stuff, glad it seem plausible in the medium term..

@moocloud_matt that's really true. My concern is that for example, when user uses it in public computer in laboratory for example, and they totally forget to log out manually. This can be an issue. For public use in research team or something, I might suggest 2FA, but it is no use too, if it keep the token alive. Alternatively, editing the config file in Nextcloud seemed to do the trick.

@jlx89 said in App Pages: This issue also affects admins like me who have to scroll through ~45 apps to find what I am looking for. I tend to filter by group or domain first, or just use the search, to avoid excessive scrolling (but, yeah, before I got into that habit I scrolled lots)

@sam_uk I'm interested in this use case too. We want to incubate groups on our Cloudron until they've reached a size where they can afford their own.

@marcusquinn because it already exists

@luckow Yes, similar view to the aliases ones where all are listed for the mailbox user.

I would love this for the app images. Ideally a build which was made today from a git tag and made 10 days ago from the same git tag should result in the same docker image. But currently, it doesn't. I don't know if this is a solved problem for docker. If there's any docs/ideas here, would be good to know.

DNSBLs are configurable in 6.4

@fbartels I do believe you.

There is a "Spam" filter type in next release - 6.4

@girish what about just a normal organization level rights separation? I mean - it's really two different set of roles: 1st line support, dealing with mailboxes 2nd or 3rd, making sure the system and services are up and running. I don't need hiding anything, I just want to ensure my users can manage they mailboxes and users for they own. For now I have to temporary give admin permissions to the 1st line and that's kind of risky...

@girish WHOOP!!! Thank you!!

@fbartels Optimism and hope? /s Great points.