From a3000940f75cd034bb0f9afa161dcde061918ddf Mon Sep 17 00:00:00 2001 From: Steve Howell Date: Sat, 22 Dec 2018 15:53:47 +0000 Subject: [PATCH] Remove Slack/PHP link to fix builds. The link is broken, and I'm not sure we want this paragraph in there, as it's somewhat speculative (we don't know how extensively Slack uses PHP any more, nor do we know how much of a factor it is in any security issues) and is probably mostly preaching to the choir. The "bounty" link should suffice. --- templates/zerver/security.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/templates/zerver/security.md b/templates/zerver/security.md index 8d2a3b53cf..1968e5fa9d 100644 --- a/templates/zerver/security.md +++ b/templates/zerver/security.md @@ -146,11 +146,7 @@ the industry: These security practices matter! Slack, the most popular SaaS team chat provider, has needed to award [hundreds of bounties](https://hackerone.com/slack) for security bugs found -by security researchers outside the company. This incredible number of -discovered vulnerabilities likely results from Slack not following secure -development practices (e.g. Slack uses a -[famously insecure](https://www.quora.com/Why-is-PHP-hated-by-so-many-developers/answer/Anders-Kaseorg) -programming language as the core language for their product). +by security researchers outside the company. ## Further reading