Skip to content

Commit 2c74240

Browse files
committed
Updated security.md
1 parent 90da40f commit 2c74240

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

SECURITY.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,8 @@ A:
100100
like like dashboards, chat, kanban. That is the point in any realtime web framework in any programming language.
101101
- Yes, you should check with Meteor DevTools Evolved Chromium/Firefox extension that at minimongo is only text that user has permission to see.
102102
- Do checking as logged in user, and logged out user.
103-
- Check permissions and sanitize before allowing some change, because someone could modify content of input field, PubSub/websocket data, etc.
103+
- Check permissions and sanitize before allowing some change, because someone could modify content of input field,
104+
PubSub/websocket data (for example with Burp Suite Community Edition), etc.
104105
- If you have REST API, also check that only those that have login token, and have permission, can view or edit text
105106
- You should not include any data user is not allowed to see. Not to webpage text, not to websockets/PubSub, etc.
106107
- Minimongo should not have password hashes PubSub https://wekan.github.io/hall-of-fame/userbleed/

0 commit comments

Comments
 (0)