Re:Signal Desktop beta now publicly available
by mellamoyo on Thursday May 05, 2016 @11:20AM
(#11636867)
> Just what sort of obscenely restrictive firewall are you behind?
Many companies block outbound on non-well known ports, for various reasons. tcp/443 is almost always available though.
Re:Signal Desktop beta now publicly available
by simoncion on Thursday May 05, 2016 @04:31PM
(#11639443)
> Many companies block outbound on non-well known ports...
Mmmhmm. Yeah, I'm aware of that. :) However, click170 made no mention of a corporate firewall. He said:
> I just wish Signal was easier to get through a firewall.
Which is dramatically at odds with my and my friends experience with Signal; namely that it passes through firewalls with no configuration required.
If he would have mentioned that it was a corporate firewall that he was trying to get through, I expect his comment would have been much less popular, and much less confusing. :)
That's really, really strange. I sit behind an IPv4 NATting router whose policy is "default REJECT unless the packet is related to a connection that conntrack knows about". [0] The device also runs UPnP, but Signal never attempts to forward any ports. Full disclosure: I have good IPv6 service, but textsecure-service-ca.whispersystems.org doesn't have any AAAA records, so I don't see what that would have to do with anything.
My friends and I can use both Signal text and voice messaging without issue.
Just what sort of obscenely restrictive firewall are you behind?
[0] You know, a typical NAT firewall configuration.