[kratoss1812]

Thanks !

[Netty]

What a shame that this is still not patched. I've got a friend who is targeted by persons who aren't even playing.
I am assuming they can somehow connect through GOTV? Or the SteamID alone?

Does anyone know of any efficient way of avoiding being auto-disconnected by the exploit of such an attacker? So that at least avoiding the targeted attacks becomes possible, and random encounters will be the only threat.

[JLmelenchon]

Happens on Left 4 Dead 2 too...

[backwards]

Originally Posted by Netty What a shame that this is still not patched. I've got a friend who is targeted by persons who aren't even playing. I am assuming they can somehow connect through GOTV? Or the SteamID alone? Does anyone know of any efficient way of avoiding being auto-disconnected by the exploit of such an attacker? So that at least avoiding the targeted attacks becomes possible, and random encounters will be the only threat.

If they are targeting your friend by his account, you can tell him to make his profile private so they cant track what servers he currently is in. Many ddos attacks exist that work on source engine servers remotely (without being connected in-game). If you have repeat offenders and need help with specific exploits, you can contact me here or on discord backwards#8236. I can try to help but I don't have as much free time.

[VYRNACH_GAMING]

is it possible to implement this for Left 4 Dead 2 as well? I'm relatively new to sourcepawn development

[noto3]

L4D2 could use this fix as well

[cravenge]

Originally Posted by JLmelenchon Happens on Left 4 Dead 2 too...

Originally Posted by VYRNACH_GAMING is it possible to implement this for Left 4 Dead 2 as well? I'm relatively new to sourcepawn development

Originally Posted by noto3 L4D2 could use this fix as well

Untested. Also merged the other fix from here since they originate from the same source

* Transitioned to new syntax
+ Compatibility for both L4D games

[finishlast]

L4D1

No idea what I did wrong

L 02/06/2022 - 19:59:11: [SM] Exception reported: Offset for "ProcessPacketHeader_CorruptedWarning" is incorrect!
L 02/06/2022 - 19:59:11: [SM] Blaming: block_packet_exploits.smx
L 02/06/2022 - 19:59:11: [SM] Call stack trace:
L 02/06/2022 - 19:59:11: [SM] [0] SetFailState
L 02/06/2022 - 19:59:11: [SM] [1] Line 103, block_packet_exploits.sp::OnPluginStart
L 02/06/2022 - 19:59:11: [SM] Unable to load plugin "block_packet_exploits.smx": Error detected in plugin startup (see error logs)
L 02/06/2022 - 19:59:14: Error log file session closed.

[cravenge]

Originally Posted by finishlast L4D1 No idea what I did wrong L 02/06/2022 - 19:59:11: [SM] Exception reported: Offset for "ProcessPacketHeader_CorruptedWarning" is incorrect! L 02/06/2022 - 19:59:11: [SM] Blaming: block_packet_exploits.smx L 02/06/2022 - 19:59:11: [SM] Call stack trace: L 02/06/2022 - 19:59:11: [SM] [0] SetFailState L 02/06/2022 - 19:59:11: [SM] [1] Line 103, block_packet_exploits.sp::OnPluginStart L 02/06/2022 - 19:59:11: [SM] Unable to load plugin "block_packet_exploits.smx": Error detected in plugin startup (see error logs) L 02/06/2022 - 19:59:14: Error log file session closed.

Linux or Windows?

[finishlast]

Linux