News for hackers. Stuff that matters.
Re:How Slack Stays Secure During Hyper Growth by packetized on Friday January 19, 2018 @02:30PM (#16188994)
It’s somewhat harder to be a Searchable Log of All (Company|Current) Knowledge if you utilize end-to-end encryption. Where are the ends?
Re:How Slack Stays Secure During Hyper Growth by meritt on Friday January 19, 2018 @02:33PM (#16189032)
This is my biggest objection to Slack. Give me an application/container/whatever I can run on our network instead. I do not trust them with my entire company chat history stored in plaintext on the same cluster as every other company.
Re:How Slack Stays Secure During Hyper Growth by BoorishBears on Friday January 19, 2018 @02:40PM (#16189078)
I feel like more often than not, organizations apply this logic to SaaSes that offers on-prem installations, and choose the on-prem over the hosted solution...

only to leave the installation out of date with critical vulnerabilities and missing features that the hosted installation would be on top of.

Re:How Slack Stays Secure During Hyper Growth by cortesoft on Friday January 19, 2018 @03:15PM (#16189383)
There is nothing stopping an on-prem appliance from being able to automatically update. Of course, once you do that, you are again putting trust back into the third party, so you lose some of what you gained.
Re:How Slack Stays Secure During Hyper Growth by BoorishBears on Friday January 19, 2018 @04:27PM (#16190025)
I don't think I've ever seen an on-prem application that self updated without manual intervention. I'm sure it exists, but it doesn't seem common.

Probably because in general self-updating goes against the control on-prem is supposed to give enterprises, especially when they're afraid of breaking critical workflows.

Re:How Slack Stays Secure During Hyper Growth by hueving on Friday January 19, 2018 @05:47PM (#16190649)
If it's not exposed to the internet, an out of date on-prem is still better than everything on a massive centralized public vendor server that 5 nation states are hacked into.
Re:How Slack Stays Secure During Hyper Growth by BoorishBears on Saturday January 20, 2018 @01:37PM (#16194665)
GitLab had a permission escalation issue that I saw unpatched on an on-Prem install. Contractors accessing it via VPN (and even local employees) would have been able to access repos and actions they didn’t have permission to access.

And it’s not like nation states can’t attack companies directly.

Re:How Slack Stays Secure During Hyper Growth by hueving on Saturday January 20, 2018 @10:47PM (#16196769)
Nation states only attack companies they care about. That's the point. Once you have your info on slack, you share the fate with the million other companies that nation states might care about.
Re:How Slack Stays Secure During Hyper Growth by praneshp on Friday January 19, 2018 @07:00PM (#16191065)
If 5 nation states hacked into the centralized public vendor they'll find a way to get into someone's on-prem version of the same, especially if they are the type to let it go very out of date.
Re:How Slack Stays Secure During Hyper Growth by hueving on Friday January 19, 2018 @11:35PM (#16192074)
The difference is that they will only hack into your on-prem solution if you are the target. With a central service, all of slack's million customers get compromised because of one single hack.
Re:How Slack Stays Secure During Hyper Growth by praneshp on Saturday January 20, 2018 @07:44PM (#16196283)
Correct, I didn't think of that.
Re:How Slack Stays Secure During Hyper Growth by lima on Friday January 19, 2018 @02:44PM (#16189114)
Nowadays there are excellent self-hosted alternatives (Zulip, Mattermost, Rocket Chat...).

That being said: A company-wide Discourse forum works much better for knowledge sharing and discussions.

Re:How Slack Stays Secure During Hyper Growth by qznc on Saturday January 20, 2018 @02:31AM (#16192499)
Has anybody ever merged chat and forums? At least integrate them so tightly that switching back and forth is fluid.
Re:How Slack Stays Secure During Hyper Growth by Tushon on Friday January 19, 2018 @02:46PM (#16189131)
That's not what they are ever going to provide, like the parent comment indicated because it isn't their goal. Companies or individuals which need your requirement should/are already using a competitor that does allow you to do so, with all the limitations that the extra security gets you (search, integrations, etc), e.g. mattermost or rocket.
Re:How Slack Stays Secure During Hyper Growth by okreallywtf on Friday January 19, 2018 @02:34PM (#16189037)
Would allowing organizations to manage their own key(s) suffice? If all of the stored data was encrypted by the users (even if it was a single key for a client organization), that would do a lot. You would have to compromise the private key(s) for the organization as well as Slacks (now useless) data.
Re:How Slack Stays Secure During Hyper Growth by dsacco on Friday January 19, 2018 @02:50PM (#16189165)
> Would allowing organizations to manage their own key(s) suffice?

No. Slack does not implement searching logic on the client. If the key is only known to the client, and the search logic is only known to the server, you can't search anything.

End-to-end encryption is fundamentally incompatible with server-side search, because it mandates that the secret key can never leave the client. You can't reconcile these two features without efficient homomorphic encryption (which does not exist yet, and will not exist for the foreseeable future in any practical sense).

Re:How Slack Stays Secure During Hyper Growth by majormajor on Friday January 19, 2018 @02:57PM (#16189229)
It could be compatible with hosted server-side search, no? (Requiring a certain amount of trust that it doesn't phone home, but that's true for a search-less encrypted client as well.)

The move to 3rd party hosting for super-sensitive internal stuff like this baffles me.

Re:How Slack Stays Secure During Hyper Growth by dsacco on Friday January 19, 2018 @03:10PM (#16189349)
Yes, that would be fine and is fully realizable. In the client-server model of end-to-end encryption, a server self-hosted by the user is isomorphic with a user's client. They're effectively the same thing.

The tricky part here is defining who the user is. If you're implementing end-to-end encryption for data on a per-employee basis, you're back to square one with a self-hosted server. But if you're implementing end-to-end encryption for data on a per-organization basis, and the organization has a self-hosted instance it controls, then yes, end-to-end encryption is compatible with organization-wide message search.

Re:How Slack Stays Secure During Hyper Growth by jpalomaki on Friday January 19, 2018 @03:50PM (#16189679)
Could work for limited search. For example each term in search index encrypted by the company key. Client passes is also encrypted search term.

Actual content of the messages could be encrypted separately. Client would send separately the selected terms for indexing and the content for each message.

Re:How Slack Stays Secure During Hyper Growth by meritt on Friday January 19, 2018 @02:39PM (#16189071)
How does Slack provide a search service if the data is encrypted by keys they do not control?
Re:How Slack Stays Secure During Hyper Growth by voidmain on Friday January 19, 2018 @05:17PM (#16190387)
The client incrementally builds a search index, encrypts it using an appropriate random access encryption primitive, and writes it to the cloud encrypted. At search time it reads as necessary from the encrypted index. (This allows some light traffic analysis; if you can't tolerate that the client can store a copy of the entire index)
Re:How Slack Stays Secure During Hyper Growth by humanfromearth on Friday January 19, 2018 @07:34PM (#16191249)
What search implements this?
Re:How Slack Stays Secure During Hyper Growth by nerfhammer on Friday January 19, 2018 @04:12PM (#16189897)
run the tokenizer on the client side, client submits encrypted tokens to the search index.

or don't provide a search service, have client have its own local index.

Re:How Slack Stays Secure During Hyper Growth by meritt on Friday January 19, 2018 @04:59PM (#16190235)
> run the tokenizer on the client side, client submits encrypted tokens to the search index.

That would be an incredibly insecure method of encryption.

> or don't provide a search service, have client have its own local index.

Yep, I would prefer an on-prem solution.

Re:How Slack Stays Secure During Hyper Growth by okreallywtf on Friday January 19, 2018 @02:52PM (#16189186)
I see your point. Is it possible to achieve that type of functionality with a reasonable expectation of security?
Re:How Slack Stays Secure During Hyper Growth by cortesoft on Friday January 19, 2018 @03:13PM (#16189369)
Well, if you want slack to be able to search chats history, it needs to be able to access it in some way.

So if your 'resonable expectation of security' involves slack not being able to read your chat history, you are going to have to give up search.

Otherwise, the reasonable expectation of security will have to rely on trusting slack to properly secure their side of things.

Re:How Slack Stays Secure During Hyper Growth by empath75 on Friday January 19, 2018 @04:04PM (#16189823)
It seems like being a searchable log of all company knowledge would make it super important to have encrypted.