News for hackers. Stuff that matters.
Re:Running your own secure communication service with Matrix... by mgbmtl on Tuesday April 07, 2020 @12:17PM (#22804562)
Any suggestions on simple auth methods to avoid running an open Jitsi server?

Last time I tested it, it seemed to be very open by default, letting anyone create meetings. I got lost when digging deeper.

If I install-and-forget, I want to avoid situations where strangers are using my Jitsi server and overloading the system, or pretending to be our company. Last I checked, it was not possible to have simple auth, or monitor/list calls.

I also run an Asterisk VoIP server with a WebRTC bridge (because most Linux SIP clients have terrible usability). That can make one pretty paranoid :)

Re:Running your own secure communication service with Matrix... by plett on Tuesday April 07, 2020 @12:36PM (#22804732)
Yes, I installed Jitsi Meet over the weekend and enabled auth so you need credentials to start a new conference, but anyone with the link (and optionally password too) can join unauthenticated.

I followed these instructions to add the auth https://github.com/jitsi/jicofo#secure-domain

Re:Running your own secure communication service with Matrix... by jvanveen on Tuesday April 07, 2020 @04:18PM (#22807069)
I've been experimenting with Asterisk WebRTC (video & audio) and developing a SIP + P2P webphone for some time now. Quite close to something that's useable imho. See https://github.com/garage11/ca11 in case you're interested
Re:Running your own secure communication service with Matrix... by esamueljohnson on Tuesday April 07, 2020 @11:01PM (#22809647)
Re:Running your own secure communication service with Matrix... by johnmaguire2013 on Tuesday April 07, 2020 @02:52PM (#22806248)
You could use something like the Duo Network Gateway or Cloudflare Access to protect it.
Re:Running your own secure communication service with Matrix... by fock on Tuesday April 07, 2020 @12:22PM (#22804615)
my university' setup has something asking for "host credentials" before starting the session, so I think it's possible. If it's just for internal use, one could just put basic HTTP(s)-auth in front?