realducksoft

3 ms·

1. 1.▲
   Signal ignores proxy censorship vulnerability, bans researchers(bleepingcomputer.com)

   36 points by realducksoft 6y ago|6 comments
2. 2.▲
   by realducksoft 6y ago

   Things has been updated. Signal banned @studentmain and @ducksoft from their GitHub organzation.
3. 3.▲
   by realducksoft 6y ago

   So guys I've been blocked. See: https://web.archive.org/web/20210206065553/https://community...
4. 4.▲
   by realducksoft 6y ago

   -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I am DuckSoft on GitHub and I prove my identity by GPG signing this message. I am not typing too fast, nor pasting all my stuffs into the comment area. I just put a link to the GitHub issue. T
5. 5.▲
   by realducksoft 6y ago

   Signal just closed their issue function there. See here: https://github.com/net4people/bbs/issues/60
6. 6.▲
   by realducksoft 6y ago

   This proxy failed to be probing resistant. The PoC code is released by studentmain: https://github.com/signalapp/Signal-TLS-Proxy/issues/3#issue...
7. 7.▲
   by realducksoft 6y ago

   Here is an interesting discussion: https://github.com/signalapp/Signal-TLS-Proxy/issues/3
8. 8.▲
   by realducksoft 6y ago

   Damn, I've read the code. This won't work against an active probe. Censors just use signal domains and non-signal domains to test your proxy. If signal domains get passed and non-signal domains got denied, you are fucked. Besides,