Live data from Hacker News

Slack enables customers to control their encryption keys in enterprise version

techcrunch.com

91–100 of 178 posts

Re: Slack enables customers to control their encryption keys in enterprise version

#91
post #87

How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/

Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?

Re: Slack enables customers to control their encryption keys in enterprise version

#92
post #79

Earlier quoted context omitted.

The article says it’s only open to enterprise customers. Computing freedom you have to pay a ton for is not really freedom. It’s really not even close to the control of IRC.

2 Options as I see it: Either don't use Slack or try to gather consensus and change things

Using Slack isn’t really a choice for most people, but I agree, coming up with alternatives is important.

Re: Slack enables customers to control their encryption keys in enterprise version

#93
post #58

Earlier quoted context omitted.

The article says it’s only open to enterprise customers. Computing freedom you have to pay a ton for is not really freedom. It’s really not even close to the control of IRC.

Is it not worth Linux running on mainframes because mainframes are expensive? Is it not worth Kerberos being free software because the only real users of Kerberos are enterprises? Computing freedom for anyone is computing freedom, and contributes to a norm of user control instead of service provider control. This step is a very small step, and it only affects a few users. But it's still a step in the right direction.…

Both of the technologies you named as examples are free and open. Anyone can inspect them and deploy them on their own. Slack isn’t like that unfortunately. This is a move to add another feature that will attract enterprise customers, I would doubt that even Slack themselves would proclaim this as a move towards greater software freedom.

Re: Slack enables customers to control their encryption keys in enterprise version

#94
post #36

Earlier quoted context omitted.

>All it takes is for a admin (or hacked admin account) to change the password of the target slack user and login as said user to view all their private messages. An admin cannot change a user's password. You can enable an account wide feature which allows admins to view all messages but that's separate and costs money. Also not what you described.

If you're using SSO, which almost every big customer does, you can usually do a password reset in the SSO itself. Also I'm pretty sure a Slack admin can change a user's email address, at which point they can trigger a password reset.

It does email the person you made the change though. If you control the email system, then you could do it silently.

Re: Slack enables customers to control their encryption keys in enterprise version

#95
post #91
post #87

How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/

Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?

Symphony's chat tool is a Slack competitor where customers can control the keys, including via HSM. On the surface it is similar to what this news is announcing Slack added to its own tool:

https://symphony.com/product/messaging-and-productivity

Re: Slack enables customers to control their encryption keys in enterprise version

#96
post #91
post #87

How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/

Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?

Can you clarify? They both offer chatrooms and depending on your definition of webapp framework they both are as well (external app integration, bots...).

Re: Slack enables customers to control their encryption keys in enterprise version

#97
post #79

Earlier quoted context omitted.

2 Options as I see it: Either don't use Slack or try to gather consensus and change things

Using Slack isn’t really a choice for most people, but I agree, coming up with alternatives is important.

Using Slack is a choice for someone in your organization, even if you aren't that person. You probably also don't get unilateral control over your working hours, pay, and office.

Re: Slack enables customers to control their encryption keys in enterprise version

#98
Maybe this is more interesting than I initially thought. I was thinking this would just the encryption keys used to store the information for your whole organization Slack account. Instead, the keys seem to be much more granular, since you can revoke access to a single file, specific channel, workspace or organization level. [1]

I see one benefit of this being able to securely throw away data. Like if you are doing work for customer XYZ and chatting about it on the corresponding channel you can throw away the keys for the channel when the project ends.

Wonder how all this granularity works together with the search functionality. Or maybe they maintain per channel search index that can be covered by a separate key.

[1] https://slackhq.com/enterprise-key-management

Re: Slack enables customers to control their encryption keys in enterprise version

#99
post #61

Earlier quoted context omitted.

It's pretty clear many customers don't want control, they want features, and irc lacks those.

Not true, Slack is actually pretty far behind on terms of features. It is true that people like the better looking, easier to use technology however.

More features isn't always better. I already find Slack very overwhelming.

Re: Slack enables customers to control their encryption keys in enterprise version

#100
post #91
post #87

How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/

Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?

You're definitely confusing with Symfony, the PHP framework. As others pointed out, Symphony is a Slack competitor.
Post reply on HN