News for hackers. Stuff that matters.
Re:Looking back at how Signal works by billme on Friday June 05, 2020 @07:30PM (#23435191)
As far as I know, while the DevOps code is not open source, the server and app code are on GitHub; that is you’re able to roll your own version however it defined by the licensing; recent attack on Signal by security researcher used a self-compiled app as a proof of concept; Signal patched the issue.
Re:Looking back at how Signal works by jlund on Friday June 05, 2020 @08:57PM (#23435816)
Just to clarify, the bug you're talking about was in WebRTC. We submitted a patch upstream:

https://webrtc-review.googlesource.com/c/src/+/175960

Re:Looking back at how Signal works by billme on Friday June 05, 2020 @09:14PM (#23435913)
Right, here’s another comment on the topic by Signal staff too: https://news.ycombinator.com/user?id=pthatcherg
Re:Looking back at how Signal works by solinent on Saturday June 06, 2020 @12:18PM (#23440213)
I didn't mean to imply Signal wasn't open-source, just that it was based on TextSecure and can be forked.

If the commercial entity fails or is held liable, we just need a distributed profile system, should be easy enough.