[blog] 01/01: 107: tweak opensuse breach coverage

[Daniel Shahaf]

This is an automated email from the git hooks/post-receive script.

danielsh-guest pushed a commit to branch master
in repository blog.

commit 6eefad1022ceb937ba3b04a8c8f4ca9dd5176c73
Author: Daniel Shahaf <danielsh at apache.org>
Date:   Sun May 14 11:19:25 2017 +0000

    107: tweak opensuse breach coverage
---
 drafts/107.mdwn | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drafts/107.mdwn b/drafts/107.mdwn
index d23e0ee..feeb960 100644
--- a/drafts/107.mdwn
+++ b/drafts/107.mdwn
@@ -1,8 +1,8 @@
 Media coverage:
 
-[openSUSE had to report a security breach in their infrastructure, including their build services](https://lists.opensuse.org/opensuse-announce/2017-05/msg00000.html) and while they state that the scope and impact is still unclear, it is a pretty clear example that noone can rely on being able to secure their infrastructure all the times. Reproducible Builds also cannot do that, but they allow independent verification of the build results at least.
+[openSUSE has had a security breach in their infrastructure, including their build services](https://lists.opensuse.org/opensuse-announce/2017-05/msg00000.html).  While (as of this writing) the scope and impact are still unclear, this incident illustrates that no one can rely on being able to secure their infrastructure at all times. Reproducible Builds cannot do that either, but they help mitigate the problem by allowing independent verification of the build results.
 
-(And please don't get us wrong: this can happen to *anyone*. Kudos to openSUSE for being open about it. Now let's continue work on reproducible builds everywhere!)
+(And please don't get us wrong: this can happen to *anyone*. Kudos to openSUSE for being open about it. Now let's continue working on reproducible builds everywhere!)
 
 Toolchain:
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/blog.git