[hlds] Nehox Panel
Hi, Has anyone used Nehox game panel ,? Any reviews for the same would be appretiated. Thanks, Sachin ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
[hlds] Pyro Teamkilling Glitch
Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Pyro Teamkilling Glitch
I had noticed a teamkilling glitch for pyros as well, but could not determine how it was done, and wasn't going to mention until I could replicate it. Load off my back, thank goodness few players know of it. On 4/13/2012 9:51 AM, Jason wrote: Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Pyro Teamkilling Glitch
Unfortunately, it looks like some super awesome people have already made a video on YouTube with instruction son how to do it and someone made a Reddit thread... I'm sure it'll be on SPUF in no time as well. Hopefully this gets patched before the weekend. On Fri, Apr 13, 2012 at 10:01 AM, Crazed Gunman bsr.crazedgun...@gmail.comwrote: I had noticed a teamkilling glitch for pyros as well, but could not determine how it was done, and wasn't going to mention until I could replicate it. Load off my back, thank goodness few players know of it. On 4/13/2012 9:51 AM, Jason wrote: Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit:https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Pyro Teamkilling Glitch
I am actually subscribed to a person on Youtube who posts TF2 exploits (so I can know what to expect) and they posted a video about this yesterday. I haven't run into it on my server, and I actually tried it on a few friends on my server to no avail, but it still needs to get patched. On Fri, Apr 13, 2012 at 10:51 AM, Jason pctool...@gmail.com wrote: Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Pyro Teamkilling Glitch
I remember the same glitch for the cow mangler, exactly same way to do, I'm not sure if it was fixed.. On Fri, Apr 13, 2012 at 12:21 PM, Daniel Barreiro dbarreiro1...@gmail.comwrote: I am actually subscribed to a person on Youtube who posts TF2 exploits (so I can know what to expect) and they posted a video about this yesterday. I haven't run into it on my server, and I actually tried it on a few friends on my server to no avail, but it still needs to get patched. On Fri, Apr 13, 2012 at 10:51 AM, Jason pctool...@gmail.com wrote: Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] HLDS Update Tool released
I dont suppose there is an option such as -nonverbose to prevent the huge amount of diagnostic lines from being displayed, for example for automated applications? On 2012/04/12 23:43, Fletcher Dunn wrote: A new version of the HLDS Update Tool has been released. The tool should automatically self-update the next time you run it. (Linux users may need to re-run the tool after it self-updates to complete the installation operation that was intended when launching the tool.) Changes: * Added significant diagnostic output * Fix bug causing the tool to restart the update process all over from the beginning if there was an error with a single depot. * Fix spurious connection reset by peer error when closing connection to content server, which could cause the update to restart from the beginning. * Tool will now reuse a connection to a depot, rather than disconnecting and reconnecting * If the determines in the first pass that no files would actually be updated from a particular depot, it will no longer needlessly connect to that depot in the second pass * Added -nobootstrapupdate option Basically, we fixed a few of the most egregious things the tool was doing that make a slow update much slower. Queuing to connect to a content server still takes up the bulk of the update time during peak times after a major update is released; so don't expect miracles. However, we are hopeful that most users will see modest speedup. We also added quite verbose diagnostic output, so at least you can tell what the tool is doing. Be aware that this output may contain what appear to be errors, especially when the tool is trying to connect to a content server. Failures to connect are normal and the tool has always experienced them and automatically retried. The only thing new is that it is telling you what it is doing. Linux users: If you get the error message Bad uSizeOfSignature, then you probably have a bad version of the tool, which was posted mistakenly for a few hours yesterday. To get unstuck, replace the executable named steam with this one: http://media.steampowered.com/apps/440/linuxhldsupdatetool_48/steam Thanks to those of you who helped beta test this tool. Thanks, Fletcher ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] HLDS Update Tool released
If it's automated why do you care about the amount of output? Surely you aren't going to be looking at the output, and if you are, then something probably went wrong. In which case, the output is helpful. I can see absolutely 0 advantages, and several disadvantages, to disabling verbose output. Kind regards, *Saul Rennison* On 13 April 2012 17:29, Dominik Friedrichs d...@forlix.org wrote: I dont suppose there is an option such as -nonverbose to prevent the huge amount of diagnostic lines from being displayed, for example for automated applications? On 2012/04/12 23:43, Fletcher Dunn wrote: A new version of the HLDS Update Tool has been released. The tool should automatically self-update the next time you run it. (Linux users may need to re-run the tool after it self-updates to complete the installation operation that was intended when launching the tool.) Changes: * Added significant diagnostic output * Fix bug causing the tool to restart the update process all over from the beginning if there was an error with a single depot. * Fix spurious connection reset by peer error when closing connection to content server, which could cause the update to restart from the beginning. * Tool will now reuse a connection to a depot, rather than disconnecting and reconnecting * If the determines in the first pass that no files would actually be updated from a particular depot, it will no longer needlessly connect to that depot in the second pass * Added -nobootstrapupdate option Basically, we fixed a few of the most egregious things the tool was doing that make a slow update much slower. Queuing to connect to a content server still takes up the bulk of the update time during peak times after a major update is released; so don't expect miracles. However, we are hopeful that most users will see modest speedup. We also added quite verbose diagnostic output, so at least you can tell what the tool is doing. Be aware that this output may contain what appear to be errors, especially when the tool is trying to connect to a content server. Failures to connect are normal and the tool has always experienced them and automatically retried. The only thing new is that it is telling you what it is doing. Linux users: If you get the error message Bad uSizeOfSignature, then you probably have a bad version of the tool, which was posted mistakenly for a few hours yesterday. To get unstuck, replace the executable named steam with this one: http://media.steampowered.com/**apps/440/linuxhldsupdatetool_**48/steamhttp://media.steampowered.com/apps/440/linuxhldsupdatetool_48/steam Thanks to those of you who helped beta test this tool. Thanks, Fletcher __**_ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hldshttps://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds __**_ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hldshttps://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] HLDS Update Tool released
I suggest you output to a file but then the console output is gone. Sent from my iPhone 4 On Apr 13, 2012, at 9:36 AM, Saul Rennison saul.renni...@gmail.com wrote: If it's automated why do you care about the amount of output? Surely you aren't going to be looking at the output, and if you are, then something probably went wrong. In which case, the output is helpful. I can see absolutely 0 advantages, and several disadvantages, to disabling verbose output. Kind regards, Saul Rennison On 13 April 2012 17:29, Dominik Friedrichs d...@forlix.org wrote: I dont suppose there is an option such as -nonverbose to prevent the huge amount of diagnostic lines from being displayed, for example for automated applications? On 2012/04/12 23:43, Fletcher Dunn wrote: A new version of the HLDS Update Tool has been released. The tool should automatically self-update the next time you run it. (Linux users may need to re-run the tool after it self-updates to complete the installation operation that was intended when launching the tool.) Changes: * Added significant diagnostic output * Fix bug causing the tool to restart the update process all over from the beginning if there was an error with a single depot. * Fix spurious connection reset by peer error when closing connection to content server, which could cause the update to restart from the beginning. * Tool will now reuse a connection to a depot, rather than disconnecting and reconnecting * If the determines in the first pass that no files would actually be updated from a particular depot, it will no longer needlessly connect to that depot in the second pass * Added -nobootstrapupdate option Basically, we fixed a few of the most egregious things the tool was doing that make a slow update much slower. Queuing to connect to a content server still takes up the bulk of the update time during peak times after a major update is released; so don't expect miracles. However, we are hopeful that most users will see modest speedup. We also added quite verbose diagnostic output, so at least you can tell what the tool is doing. Be aware that this output may contain what appear to be errors, especially when the tool is trying to connect to a content server. Failures to connect are normal and the tool has always experienced them and automatically retried. The only thing new is that it is telling you what it is doing. Linux users: If you get the error message Bad uSizeOfSignature, then you probably have a bad version of the tool, which was posted mistakenly for a few hours yesterday. To get unstuck, replace the executable named steam with this one: http://media.steampowered.com/apps/440/linuxhldsupdatetool_48/steam Thanks to those of you who helped beta test this tool. Thanks, Fletcher ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] HLDS Update Tool released
The thing is I'm reading the output via pipe into my server monitor tool to check if at the end it says update successful. Now the amount of text is so huge that I have to change my methods of handling/storing it in the code (curse me for having used a fixed size array), and I'm not very keen on working on that right now :)) On 2012/04/13 18:36, Saul Rennison wrote: If it's automated why do you care about the amount of output? Surely you aren't going to be looking at the output, and if you are, then something probably went wrong. In which case, the output is helpful. I can see absolutely 0 advantages, and several disadvantages, to disabling verbose output. Kind regards, *Saul Rennison* On 13 April 2012 17:29, Dominik Friedrichs d...@forlix.org mailto:d...@forlix.org wrote: I dont suppose there is an option such as -nonverbose to prevent the huge amount of diagnostic lines from being displayed, for example for automated applications? On 2012/04/12 23:43, Fletcher Dunn wrote: A new version of the HLDS Update Tool has been released. The tool should automatically self-update the next time you run it. (Linux users may need to re-run the tool after it self-updates to complete the installation operation that was intended when launching the tool.) Changes: * Added significant diagnostic output * Fix bug causing the tool to restart the update process all over from the beginning if there was an error with a single depot. * Fix spurious connection reset by peer error when closing connection to content server, which could cause the update to restart from the beginning. * Tool will now reuse a connection to a depot, rather than disconnecting and reconnecting * If the determines in the first pass that no files would actually be updated from a particular depot, it will no longer needlessly connect to that depot in the second pass * Added -nobootstrapupdate option Basically, we fixed a few of the most egregious things the tool was doing that make a slow update much slower. Queuing to connect to a content server still takes up the bulk of the update time during peak times after a major update is released; so don't expect miracles. However, we are hopeful that most users will see modest speedup. We also added quite verbose diagnostic output, so at least you can tell what the tool is doing. Be aware that this output may contain what appear to be errors, especially when the tool is trying to connect to a content server. Failures to connect are normal and the tool has always experienced them and automatically retried. The only thing new is that it is telling you what it is doing. Linux users: If you get the error message Bad uSizeOfSignature, then you probably have a bad version of the tool, which was posted mistakenly for a few hours yesterday. To get unstuck, replace the executable named steam with this one: http://media.steampowered.com/__apps/440/linuxhldsupdatetool___48/steam http://media.steampowered.com/apps/440/linuxhldsupdatetool_48/steam Thanks to those of you who helped beta test this tool. Thanks, Fletcher _ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] HLDS Update Tool released
Thanks for updating this! The connection reset by peer issue was really painful, especially for update scripts. One request: A a -command checkupdate flag that checks if any updates are needed (either depot versions or with -verify_all). This would allow tools like nemrun to track optional updates, and let admins see if they have any issues with -verify_all without worrying about killing the server. - Neph ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Pyro Teamkilling Glitch
Just disable spectator mode as a temp fix. From: hlds-boun...@list.valvesoftware.com [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Jason Sent: Friday, April 13, 2012 10:51 AM To: Half-Life dedicated Win32 server mailing list Subject: [hlds] Pyro Teamkilling Glitch Last night on one of our servers, a regular found a way to teamkill his teammate while playing pyro. We can replicate this consistently. Has anyone else encountered this issue? Who do I report this to -- without saying exactly how it's done so it's not widely abused until it could be potentially patched? Thanks in advance. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Nehox Panel
Seeing as it looks like something extremely new, I would say you probably won't get much of any reviews on it. It looks like they have a beta signup going on but other than that, no idea. Last announcement back in January. Doesn't look too incredibly active. On Fri, Apr 13, 2012 at 6:37 AM, Sachin Sud ad...@crazyfreakgamers.comwrote: Hi, Has anyone used Nehox game panel ,? Any reviews for the same would be appretiated. Thanks, Sachin ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Source Engine remote slowhacking exploit - how can I dump a .dem file?
First, the demo file won't record any crucial information... plus, these exploits aren't valve commands being messed up, it could be protocols being buggy; for example sending the connection packet of 300 different clients... And secondly, this reminds me of the disconnect message exploit, that would *also block FVAR*, but I wouldn't worry about that exploit, it's already fixed! On Fri, Apr 13, 2012 at 2:15 AM, Harry Strongburg harry.h...@harry.luwrote: Hi, just thought I'd tell you guys that there's a remote slowhacking exploit in the wild. Any user, who doesn't need any permissions at all on the server, and happens without ANY server modifications installed, can make all the client's on the server unresponsive. The exploit will even run just fine on Valve's official TF2 servers. Along with this, they can run seemingly any rcon command, such as say. Any command on the player's clients will give the console error FCVAR_SERVER_CAN_EXECUTE prevented server running command (this includes toggleconsole, etc). This will make your game impossible to use, until you taskkill HL2 and join a new server. In the experience I saw, this exploit doesn't work if you have SMAC installed: User was kicked for command spamming: say hi. So my point of this email is if anyone here any idea on what I can do with a demo I was recording while the exploit was run on a server I was playing on. In particular, if I could see what commands the server forced my client to run (the slowhacking commands were recorded properly in the demo), it might be a bit easier for Valve to fix up whatever the exploit is. Thanks for any suggestions. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Source Engine remote slowhacking exploit - how can I dump a .dem file?
On Fri, Apr 13, 2012 at 09:16:40PM -0300, Bruno Garcia wrote: First, the demo file won't record any crucial information... What makes you think this? The client being unusable happens if you play back the demo, so whatever (at least the clientside breakage) is, it's recorded there. plus, these exploits aren't valve commands being messed up, it could be protocols being buggy; for example sending the connection packet of 300 different clients... Making everyone on the server being unable to press buttons via FCVAR_SERVER_CAN_EXECUTE could be a buggy protocol? It's obviously something on the game level. What are you getting at here? And secondly, this reminds me of the disconnect message exploit, that would *also block FVAR*, but I wouldn't worry about that exploit, it's already fixed! Well then it's obviously different then if it was patched, but maybe related. Anyways, I sent the demo to someone reputable offlist who (hopefully) knows what he's doing. Anyone with any other suggestions please say. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
