Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Team Fortress 2 source code has leaked

techradar.com

Post reply on HN
Print view View original

121–130 of 167 posts

Re: Team Fortress 2 source code has leaked

#121

Post by hateMyIdeas »

ThomPete wrote: post #36
exabrial wrote: post #3

Cheats and hacks were already bad enough, I imagine this won't help :( Darn, one of the most fun games I like to play. Sadly, OSX Catalina killed the game for Mac users because Apple recognized the extreme demand by casual users to break all their old 32bit applications.

I literally just downloaded Steam on the mac to show my boys Team Fortress only to be met by this sad news :( I really hope something like TF2 resurfaces in some form again. I never liked the feel of Fortnite.

Install Windows? Simple enough solution

Re: Team Fortress 2 source code has leaked

#122

Post by snvzz »

Remember that, while available, it isn't legally so.

My advice is to avoid getting tainted. Do not read the code.

Of course, archivists, please do archive it. Even if Valve does never open source this, it should be possible to preserve somewhat adequately, and it should be legal to publish, at some point in the future, in some country or another.

Re: Team Fortress 2 source code has leaked

#123

Post by andbberger »

klmadfejno wrote: post #102
andbberger wrote: post #96

Earlier quoted context omitted.

I don't think you can be confident that this is F-STOP, multiple indications support that it is fan made. There is an obvious reason why F-STOP wasn't finished though: Valve never finishes anything. Episode 2 came out 13 years ago.

It could be fan made, but the camera mechanic seems to be from the source code, no? There could be MORE to the mechanic that isn't implemented but this piece at least looks lame edit: and for completeness, nowadays I feel compelled to point out that the latest half life game came out just a month ago

Right, this why I mention the thirteen years. That's what it took to get a new half life.

Re: Team Fortress 2 source code has leaked

#124

Post by swixmix »

missblit wrote: post #120
enchiridion wrote: post #115

Earlier quoted context omitted.

I'm not sure if heartbleed is a good example here, given that it was basically a new class of exploit.

Wasn't heartbleed a fairly typical buffer overflow?

the typical buffer overflow would have been caught by OpenBSD's protective malloc.

> [...] OpenSSL adds a wrapper around malloc & free so that the library will cache memory on it's own, and not free it to the protective malloc. [...] So then a bug shows up which leaks the content of memory mishandled by that layer. [...]

https://marc.info/?l=openbsd-misc&m=139698608410938&w=2

Re: Team Fortress 2 source code has leaked

#125

Post by _pmf_ »

hitpointdrew wrote: post #106
ocdtrekkie wrote: post #19

Earlier quoted context omitted.

Source code availability makes it a lot easier to find vulnerabilities. Open source code is much more likely to already have been audited better. Closed source code often depends more heavily on security by obscurity, and unexpected source release can definitely make vulnerabilities immediately apparent that weren't known prior.

> Open source code is much more likely to already have been audited better. Common wisdom. I just happens to not be true. People just aren't auditing random code on github for fun. Auditing code is hard, and time consuming. Most vulnerabilities are found by techniques like fuzzing, not by combing through thousands of lines of code.

> People just aren't auditing random code on github for fun

No, just the important code that everyone is running.

Re: Team Fortress 2 source code has leaked

#126

Post by tal8d »

rmdashrfstar wrote: post #78
MaxBarraclough wrote: post #42

Earlier quoted context omitted.

Very true, but OpenSSL in particular is rather infamous. Unfortunate given that so much relies on it. https://news.ycombinator.com/item?id=7556407

This is why the assumption that “open source code is more likely to be closely audited for vulnerabilities” is not true (even for incredibly core/important projects with a wide scope) and is potentially dangerous to rely on.

> This is why the assumption that “open source code is more likely to be closely audited for vulnerabilities” is not true...

That is a safe assumption, otherwise you'd have to believe that non-open source code is more closely audited - at greater expense, because businesses secretly prioritize security.

Re: Team Fortress 2 source code has leaked

#127

Post by selestify »

swixmix wrote: post #124
missblit wrote: post #120

Earlier quoted context omitted.

Wasn't heartbleed a fairly typical buffer overflow?

the typical buffer overflow would have been caught by OpenBSD's protective malloc. > [...] OpenSSL adds a wrapper around malloc & free so that the library will cache memory on it's own, and not free it to the protective malloc. [...] So then a bug shows up which leaks the content of memory mishandled by that layer. [...] https://marc.info/?l=openbsd-misc&m=139698608410938&w=2

Seems like that commenter is also saying that it would’ve been caught as a regular buffer overflow bug?

> OpenSSL is not developed by a responsible team.

Re: Team Fortress 2 source code has leaked

#128

Post by enchiridion »

missblit wrote: post #120
enchiridion wrote: post #115

Earlier quoted context omitted.

I'm not sure if heartbleed is a good example here, given that it was basically a new class of exploit.

Wasn't heartbleed a fairly typical buffer overflow?

I've always thought of buffer overflow as writing beyond the intended bounds of the buffer.

Heartbleed is reading beyond the intended bounds remotely. I don't think there were similar attacks before hand, but I could be wrong. I only have a base level knowledge here.

Re: Team Fortress 2 source code has leaked

#129

Post by [deleted] »

_pmf_ wrote: post #125
hitpointdrew wrote: post #106

Earlier quoted context omitted.

> Open source code is much more likely to already have been audited better. Common wisdom. I just happens to not be true. People just aren't auditing random code on github for fun. Auditing code is hard, and time consuming. Most vulnerabilities are found by techniques like fuzzing, not by combing through thousands of lines of code.

> People just aren't auditing random code on github for fun No, just the important code that everyone is running.

[deleted]

Re: Team Fortress 2 source code has leaked

#130

Post by saagarjha »

enchiridion wrote: post #128
missblit wrote: post #120

Earlier quoted context omitted.

Wasn't heartbleed a fairly typical buffer overflow?

I've always thought of buffer overflow as writing beyond the intended bounds of the buffer. Heartbleed is reading beyond the intended bounds remotely. I don't think there were similar attacks before hand, but I could be wrong. I only have a base level knowledge here.

Infoleaks are nothing new.
Post reply on HN