Earlier quoted context omitted.
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.
Slack enables customers to control their encryption keys in enterprise version
151–160 of 178 posts
Re: Slack enables customers to control their encryption keys in enterprise version
#152Earlier quoted context omitted.
Sure, but that fixes it for you, not anyone else. What's the point when the person you're talking to went offline because they went through a tunnel or momentarily closed their laptop when you sent the message? This classic HN idea that people only use Slack over IRC because it looks better/easier is a reminder of nerd hubris that prevents one from understanding people and products.
People do use Slack because it looks better and is easier to use.... the features you're talking about are possible with IRC, it just requires work that the average consumer isn't willing to do. The other half of the equation is that IRC is better in ways that consumers don't care about, yourself included.
Re: Slack enables customers to control their encryption keys in enterprise version
#153Earlier quoted context omitted.
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.
Re: Slack enables customers to control their encryption keys in enterprise version
#154Earlier 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.…
Honest question: what is it worth to me? I don't but into this "any linux usage is a win" mentality. Linux being used on tivos is worthless to me (https://www.gnu.org/proprietary/proprietary-tyrants.en.html), and it's hard to see why Linux running on hardware I will never have the opportunity to own should be worth anything to me either. Am I expected to cheer for the linux team no matter the circumstance?
Re: Slack enables customers to control their encryption keys in enterprise version
#155The title of this post makes it sound like a bad thing, but in regulated industries like Finance, firms are required to produce chat transcripts of the traders to regulators. Slack would be unusable in this industry if the firms could not capture all of the chat logs.
Re: Slack enables customers to control their encryption keys in enterprise version
#156Only available for an "additional fee" for Enterprise users. Cheeky. Also, Slack, I'd like a native MacOS app please.
It's only needed by large, highly regulated businesses, and it only works for self-hosting obviously.
Re: Slack enables customers to control their encryption keys in enterprise version
#157Earlier quoted context omitted.
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.
That's what I don't get from reading this thread. Like you said, Kerberos does have its uses outside enterprise deployments, and if you want authenticated/encrypted NFS for whatever reason it's really one of your only options.
Re: Slack enables customers to control their encryption keys in enterprise version
#158Earlier quoted context omitted.
Yeah I don't really care about Slack, it's banned at work. However, this pattern is good and IMHO should be adopted by SaaS orgs that want to appeal to enterprise/regulated customers. We have a few vendors that we're sort of pressing in this direction, and a few have come to us with similar architectural proposals to address GDPR. Specific to AWS it would be even better of the service allowed for the customer to host…
> Specific to AWS it would be even better of the service allowed for the customer to host the CMK in their own account so they can choose to import key material if they like. Looks like it does, based on https://aws.amazon.com/blogs/apn/control-access-to-your-data... "With Slack EKM, you can use KMS in your own AWS account to create a Customer Master Key (CMK) that always stays under your control. Then, using key pol…
Re: Slack enables customers to control their encryption keys in enterprise version
#159Earlier quoted context omitted.
"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…
Why 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.
Re: Slack enables customers to control their encryption keys in enterprise version
#160One thing I'm not totally clear on after reading the article is which AWS account the AWS KMS resides. Is it Slack's AWS account or the customer's?