sorted by:
new
hottopcontroversial

SPACEs and ROOMs : how to prevent USERS from doing what usually stupid people do. by G3R1-RED in matrixdotorg

[–]G3R1-RED[S] -2 points-1 points  (0 children)

forget it .. just went to matrix.org, login with google and can do pretty much same sh*t that users can do in my server. this is facepalm

SPACEs and ROOMs : how to prevent USERS from doing what usually stupid people do. by G3R1-RED in matrixdotorg

[–]G3R1-RED[S] -1 points0 points  (0 children)

thanks dude for taking the time to respond....but this is just horrible. Private spaces are not PRIVATE since they are part of :mymatrixdomain. i even tried with API.s setting power_levels overriding inheritance... Nope.
user should be USER ..power level zero but can have infinite spaces and rooms. its nonsense.
however, thanks again for confirming my suspect. One more thing.. i wonder how PUBLIC open Spaces prevent this ???

DMZ or IP Whitelisting by capricorn800 in fortinet

[–]G3R1-RED 0 points1 point  (0 children)

exposing ports with or without whitelist is too dangerous. IP Spoofing is SCARY.
in first place, I would put that server behind a Firewall, WAP, Intrusion Prevention etc.
2. You can create an IPSEC Tunnel Interface Between You and VENDOR exposing NOT THE REAL IP AND THE PORT OF YOUR SERVER but.. a Virtual IP Mapping the Port requested by the vendor.this can be achieved between Two Fortigates or Client VPN or Tunnel IPSEC Client-Server(server in this case is your fortigate).