From 96b6b97c459dda2b4bd5455d6ab61fee0287fcc2 Mon Sep 17 00:00:00 2001 From: Julius Figge Date: Wed, 16 Aug 2023 17:26:49 +0200 Subject: [PATCH] refactor --- content/blog/games/security/getting-sued-for-disclosure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/blog/games/security/getting-sued-for-disclosure.md b/content/blog/games/security/getting-sued-for-disclosure.md index 35c0b99..fb75a89 100644 --- a/content/blog/games/security/getting-sued-for-disclosure.md +++ b/content/blog/games/security/getting-sued-for-disclosure.md @@ -17,11 +17,11 @@ This Breach exposed 700.000 customers Datasets, consisting of several large germ Link to related Source from Mark Steier [in German] This Vulnerability was disclosed to the Distributor of the Software. -But instead of expressing gratitude - Steier was sued. +But instead of expressing gratitude - Steier was sued. Link to related Source [in German] After some back and forth, Steier is now facing a lawsuit after the public prosecutor's office in Cologne ruled that decompiling the source code _"requires a deep understanding of programming languages and software development"_. -Therefore he is no threated under the so called "Hackerparagraph" (§202 StGb) for _"Spying out data"_. +Therefore he is no threated under the so called "Hackerparagraph" (§202 StGb) for _"Spying out data"_. Link to related News Article from Heise [in German] ### Consequences