[Solokiller]

We don't know, they haven't said anything about that. Given that the reason not to provide support was that it takes engineering cycles and that their repository was lost that may change now, since it's all set up now.
It didn't take long to incorporate a fix i sent them, so maybe they changed their approach.

[gabuch2]

Wasn't this just a gamedll problem and not engine?

[Solokiller]

Yes, but the engine was also recompiled. The timestamp embedded at compile time for the Linux hw.so library is: 17: 35:22 Jul 5 2017

[gabuch2]

Any undocumented changes?

[Solokiller]

So far we only know of 2 fixes: a format string attack and a server crash exploit involving weapon dropping.
I'm guessing they're putting their development environment together and pushing out a beta so they can get it tested more easily once they put out the changelog.

[PRoSToTeM@]

Originally Posted by Solokiller a format string attack

It was done in the previous beta 4 years ago by alfred, wasn't it?

[Solokiller]

Must be a different attack, unless they never merged the beta to public.

[PRoSToTeM@]

Nice, now chat is broken not only in beta, but in release too.

[Solokiller]

Give me the steps to reproduce (seriously) and i'll send it to Alfred.

[PRoSToTeM@]

Ok. This update breaks backwards compatibility with older way to fix it:

message_begin(MSG_ALL, get_user_msgid("SayText"));
write_byte(0);
write_string("%s"); // or %s1
write_string(message);
message_end();

Now (in 7561) it prints only " s" or " s1", but in 6153 (release) it worked fully correctly and accurate.
It is used in some plugins, so now they are broken. Also some plugins using "%s1 : %s2" construction.

Ideally, chat fix should only fix the crash ("%s0" infinite loop and "#Spec_Help_Text ..." chat buffer overflow), but not break backward compatibility.

TextMsg is affected too.