Re:Twitter warns that private tweets were public for years
by mrspeaker on Friday January 18, 2019 @02:31PM
(#18942168)
I'm often surprised how much people share via Slack as if it's an impenetrable fortress: perfect for pasting admin passwords, keys, and incriminating opinions and business secrets... if that floodgate ever opens then it will be a crazy time for us devs!
[ Parent
| on HN ]
Re:Twitter warns that private tweets were public for years
by wool_gather on Friday January 18, 2019 @03:31PM
(#18942756)
Yeah, this drives me up a wall. I have a coworker who constantly champions the bull* static code analyzer we use catching "security" issues...and then sends around certs and keys via Slack and email. :/
Re:Twitter warns that private tweets were public for years
by enraged_camel on Friday January 18, 2019 @04:24PM
(#18943245)
Security is always a matter of cost vs. benefit, i.e. you need to weigh the cost of the risk (likelihood * impact) with the benefit of the action.
For example, I have shared credentials on Slack before, but that's because said credentials were for a non-critical system, and if hackers somehow a) hacked Slack and b) identified the information I shared and used it, the only thing they would get their hands on would be a curated collection of cat pictures with funny captions (and I don't re-use passwords).
Therefore, blanket rules like "don't share credentials on Slack" tend to miss the point. Obviously, don't share your bank account info on there. But you can totally talk about otherwise sensitive stuff if the risk profile is sufficiently negligible.
Re:Twitter warns that private tweets were public for years
by TeMPOraL on Saturday January 19, 2019 @06:29AM
(#18946480)
Sharing credentials is not a problem. The more critical ones are probably rotated regularly anyway. But it'll be fun to see all the dirty laundry getting aired publicly if and when Slack gets hacked.
Re:Twitter warns that private tweets were public for years
by leppr on Saturday January 19, 2019 @06:23AM
(#18946461)
Good time to remind that hacks notwithstanding, Slack private messages can in many occasions not be private by design (and so shouldn't be considered private to begin with): https://mashable.com/2017/10/26/slack-dms-private
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
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/