Re:Twitter warns that private tweets were public for years
by alexandercrohde on Friday January 18, 2019 @02:36PM
(#18942221)
Just as a heads up on this, slack doesn't even use HTTPS! Your employer can certainly read all private slacks on your work network, even if it's a non-work-slack workspace
[ Parent
| on HN ]
Re:Twitter warns that private tweets were public for years
by ReidZB on Friday January 18, 2019 @02:56PM
(#18942396)
Pretty sure it uses HTTPS, but if you're on a corporate network on corporate hardware, there is a real chance that there's a corporate MITM proxy that is capable of reading all of your HTTPS traffic.
Re:Twitter warns that private tweets were public for years
by isostatic on Friday January 18, 2019 @03:21PM
(#18942664)
Only if you have their root certificate trusted
Re:Twitter warns that private tweets were public for years
by doesnt_know on Friday January 18, 2019 @11:29PM
(#18945337)
From experience, if the org is doing https mitm then it almost certainly also has network device authentication (eg Cisco ICE) that would only allow corporate whitelisted devices. Usually with custom builds that would already have the corp root cert trusted.
Re:Twitter warns that private tweets were public for years
by maxxxxx on Friday January 18, 2019 @03:29PM
(#18942739)
You have to do that if you want to do any work.
Re:Twitter warns that private tweets were public for years
by judge2020 on Friday January 18, 2019 @02:58PM
(#18942417)
curl http://slack.com -v
< HTTP/1.1 302 Found
< location: https://slack.com/