3 ms·
Are you saying you had some sort of presumption of privacy on a corporate Slack account? If you did, you had it in error. If I am reading this right, this act
by jerf 8y ago
Are you saying you had some sort of presumption of privacy on a corporate Slack account?
If you did, you had it in error.
If I am reading this right, this actually reduces your exposure as an employee. Instead of your employer and Slack having full access to everything you do on that account, now your employer has full access but Slack's access is reduced substantially. (If the setup is working as I expect, Slack will still get metadata.)
- tyingq 8y agoI don't know slack internals. but I assume the employer having the key means that they now have a way to rewrite history in a way that looks cryptographically correct.
- bastawhiz 8y agoThat's not how it works. Just because you have the keys doesn't mean you have direct filesystem or database access to change what you please.
- eitland 8y agoOk, lets just make this clear: Slack is not the tool you'd want to use for anything but the most innocent work-related messages. For that it is kind of usable, not good but one of the better that will get approved by management.
- tyingq 8y agoI didn't suggest it was. Again, I don't know the internals. But generally, an entity that has keys can forge messages. There's an incremental difference between the ability to snoop and the ability to forge. There's docs on the slack API, but none for the protocol, and not much is said about the new functionality. It's certainly possible that was already there via other means, but a change in key control seems significant enough to warrant a UI indicator to me.
- jerf 8y ago"But generally, an entity that has keys can forge messages." It depends on how it's structured, and with the most natural structure, this wouldn't be true. You'd be able to forge a message with the keys to exactly the same degree that you can forge a message coming from your coworker in Slack right now; short of social engineering to steal their password, anything else that would allow you to do that right now would be a major security vulnerability in Slack. And, more to my point, one that could be fixed. Private keys here would be adding a layer of protection and making it harder, not easier, to forge anything. Of course, an employer today could also claim to have evidence that you sent X to person Y, but Slack's own records would show that you didn't. They'd have to go out of their way to make it so that merely holding the encryption key would allow you to fully forge messages. Generally speaking, this is not adding power to the system, it's actually removing it. The reason why enterprise customers want this feature is not to give the customer more power, it's to remove power from Slack, because without this feature, Slack (not your employer) could forge messages. Assuming they implement this key stuff securely, this would remove the power to forge messages from Slack, and your employer would continue to not have it.
- atomical 8y agoWhy do you believe employees are worried about the actions of Slack instead of the actions of their own employer? This change allows companies to spy on employees.
- fphhotchips 8y agoNo it doesn't! Employers have been able to read messages on Slack for ages now.
- atomical 8y agoOh, whoops. I guess they caved to pressure.
- atomical 8y ago> Are you saying you had some sort of presumption of privacy on a corporate Slack account? Slack grew because employees like me convinced their employers to start using it. The same people can also convince their companies to drop Slack and use something else. > If I am reading this right, this actually reduces your exposure as an employee. Instead of your employer and Slack having full access to everything you do on that account, now your employer has full access but Slack's access is reduced substantially. (If the setup is working as I expect, Slack will still get metadata.) It kinda sounds like you're saying that the employee has responsibility for data on Slack if there is a security breach at Slack. Either way, Slack has little interest in spying on employees and sowing discord.
- xYa1001 8y agoWhat is so controversial about this comment that it is down-voted several points? The whole thread is dominated by Slack apologists.
- ubwXY 8y agoPerhaps not in the U.S., but Europeans could definitely sue their employer if private messages are read (which Slack explicitly supports). Slack is a shady thing and I'll never install their desktop app, which presumably is full of user tracking.