Difference between revisions of "User:Sitzkrieg/Sandbox/Source code"

From Team Fortress Wiki
Jump to: navigation, search
(Re-added delete tag, mention of cheats makes no sense as this page isn't about cheats. Please discuss the tag rather than removing it entirely)
m (Removed protection from "User:Sitzkrieg/Sandbox/Source code")
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover the impact of the leak(s) and major events.'''
+
{{Merge|Unused content}}
 
 
{{Delete|See talk page section}}
 
  
 +
''This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover general information about the leak.'' 
  
 
On April 21st 2020 the source code for many [[Source]] Engine games was leaked. Team Fortress 2 was no exception to the leak, as it contained a complete early-2016 build of TF2.  
 
On April 21st 2020 the source code for many [[Source]] Engine games was leaked. Team Fortress 2 was no exception to the leak, as it contained a complete early-2016 build of TF2.  
Line 9: Line 8:
 
== RCE Scare ==  
 
== RCE Scare ==  
  
When news of the leak initially spread, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution).
+
When news of the April 2020 leak initially broke, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution).
This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected.
+
This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected. The RCE vulnerability was discovered to have never existed in the first place.  
 
    
 
    
 
== Media Response ==  
 
== Media Response ==  
  
Within weeks after the leak, media figures within the community began auditing the source code.
+
Within weeks after the April 2020 leak, media figures within the community began auditing the source code. During this time the "spaghetti code" rumors of TF2 were found to be verifiably true.  
  
 
On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments.  
 
On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments.  
  
 
== Cut Content ==
 
== Cut Content ==
 
 
Many speculated-to-exist assets and features were discovered by the source code leak.
 
Many speculated-to-exist assets and features were discovered by the source code leak.

Latest revision as of 19:26, 7 September 2024

This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover general information about the leak.

On April 21st 2020 the source code for many Source Engine games was leaked. Team Fortress 2 was no exception to the leak, as it contained a complete early-2016 build of TF2. The specific leaked build was from the major Tough Break update.

RCE Scare

When news of the April 2020 leak initially broke, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution). This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected. The RCE vulnerability was discovered to have never existed in the first place.

Media Response

Within weeks after the April 2020 leak, media figures within the community began auditing the source code. During this time the "spaghetti code" rumors of TF2 were found to be verifiably true.

On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments.

Cut Content

Many speculated-to-exist assets and features were discovered by the source code leak.