#MATTERMOST SYSTEM REQUIREMENTS HOW TO#
#MATTERMOST SYSTEM REQUIREMENTS PASSWORD#

If you're putting users on the system that you don't trust, and you don't train them in security, how do you avoid them re-using their passwords in unsafe SaaS services? How do you avoid them sharing passwords over Skype?

It's designed to be self-hosted in a private cloud. We're transparent that Mattermost Team Edition is 'modern communication behind your firewall'. Otherwise, please give time for others in the community to reflect on your comments and respond over time. We have video calling now, I don't mind jumping on. If you want to discuss with me or others closer to real time, you can join our community Mattermost server at.Over a hundred feature proposals are now existing product features. If you're looking for a different design, please consider opening a feature proposal and having it upvoted and discussed publicly-at a minimum, you should have people in your organization vote with you. We've already shared our community guidelines with you previously, I'd ask your help to act as an informed member of the community.

If you were sitting in the living room of any of the hundreds of contributors who have invested in this open source project, what tone would you use? If you feel something can be done better, please say so in a way that doesn't belittle other people's implementations or opinions. If you want to continue the discussion about Mattermost, that is absolutely welcome so long as the conversation is respectful and constructive.

#MATTERMOST SYSTEM REQUIREMENTS PASSWORD#

If you'd like to help enable the implementation of a detector of strong and weak password in our open source edition, there's an existing ticket to help do this: I think you're correct that the policy features for passwords don't necessarily create strong passwords. This conversation brings up a point on how our systems define bugs (code defects) and improvements (user experience defects, small and large features, etc.), which we have defined among core committers, but not made public, so I've opened a ticket to document this: mattermost/docs#1126 You're 100% correct that the current design is not obvious, and that breaks our requirement. We have a design principle of fast, obvious, forgiving. I've opened a ticket to address this and proposed opening a Help Wanted ticket for the community to contribute this change: I looked into this more, and while our documentation lists out which config.json parameters apply to which feature, if you're trying to infer what things do based on naming, it's not clear, and we should do a better job there.

You're right, it's not okay for the setup of Mattermost to be surprising.

Closing this so we can move to feature appreciate the feedback, The documentation matches the functionality we can't really say it's a defect. Per community guidelines feature discussions should go to feature proposal forum, and GitHub Issues are for bug reports. 3) Propose moving this discussion to feature proposal forum Having a password strength indicator is more likely to help users select strong passwords than a bunch of error messages.Įnterprise feature are about IT policy, see Manifesto for more on the principles of the open source project. The Enterprise Edition options are to enforce corporate policy, but-as you are pointing out-their ability to create strong passwords depends entirely on those policy settings. Could we have your help? 2) What is the correct way to ensure strong passwords? I believe you can help enable this feature if you choose to.

#MATTERMOST SYSTEM REQUIREMENTS HOW TO#

My ask to you is agreement on how to classify strong and weak passwords, ideally with libraries we can use to implement the password strength indicator in Team Edition. Until we have a criteria, we can't add the would you be open to discussing the feature proposal so we can have someone from the community add this? There's a feature proposal and ticket to add a password strength indicator to Team Edition as a start.

There should be some criteria for what makes a strong password. Highly appreciate your feedback, some thoughts and a request for your help: 1) What is the correct criteria for a strong password?

Mattermost system requirements