I posted this on SPUF back during the whole Free2BeKicked drama: I think the best way would be a hardware identifier exposed as part of the authentication ticket (covering the whole system, so that changing an individual component does change the ID, but this is still “stronger” than going after individual IDs). This would mean that and individual server could ban that computer, lasting only on that server. This would be saner than IP bans (the only solution to multiple accounts other than my plugin) as it wouldn’t affect multiple people as in the case of a dynamic IP, but it would also be harder to change for that individual hacker. Hardware bans work fine on a per-server case like this, they just fall apart when used by an invasive global system like VAC, because they are inherently “unfair” since someone who just “tried” a cheat (or someone used their computer) could get that computer permanently banned. Previously, this did work fine with SteamIDs because the limitation was to get a new Steam account. Since, with my idea, if it’s just a per-server ban you can join another server, where if a user continued to cheat they would just get banned again or if they didn’t they wouldn’t have any issue.
Just my 2¢. On Sat, Mar 3, 2012 at 10:29 AM, AnAkIn . <anakin...@gmail.com> wrote: > Maybe they could use the hardware information that the Steam client > already send them every time you log in? > - Network cards > - CD/DVD/Hard drives and others > (MediaType/Index/DeviceID/SerialNumber/Manufacturer) > - OS (Version, CD Key) > + more stuff > > 2012/3/3 Cameron Munroe <cmun...@cameronmunroe.com>: >> Really, how would you track this? Ip ~ no. So what? The fact is NAT is so >> extensive now that tracking via IP is ineffective at best. >> >> >> On 3/3/2012 1:43 AM, AnAkIn . wrote: >>> >>> As if Valve never thought of doing that. Back when F2P got released >>> they said they would do something against people creating multiple >>> accounts, and they never done anything. >>> >>> 2012/3/3 Rob Liu<robl...@gmail.com>: >>>> >>>> Here's my 2cents on this issue. >>>> Make Steam guard mandatory. And put a limit on how many free to play >>>> accounts a user can create? >>>> >>>> >>>> On Sat, Mar 3, 2012 at 8:50 PM, Spencer 'Voogru' MacDonald >>>> <voo...@voogru.com> wrote: >>>>> >>>>> That doesn’t do much good for things like aimbots. >>>>> >>>>> >>>>> >>>>> I personally don’t like the idea of preventing them from joining, but >>>>> simply taking away things that they might be able to abuse. My dodgeball >>>>> servers for example doesn’t allow f2p to use, or hear anyone on voice >>>>> comm. >>>>> Too many unbannables just spewing mic spam all day. >>>>> >>>>> >>>>> >>>>> - Spencer. >>>>> >>>>> >>>>> >>>>> From: hlds-boun...@list.valvesoftware.com >>>>> [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Cameron Munroe >>>>> Sent: Friday, March 02, 2012 10:22 PM >>>>> To: Half-Life dedicated Win32 server mailing list >>>>> Subject: Re: [hlds] Hackers on the rise >>>>> >>>>> >>>>> >>>>> That is like saying I will not sell my product to "greens." It is not >>>>> effective and can do way more harm then good. You might just want to >>>>> beef up >>>>> your security with sourcemod and some plugins. >>>>> >>>>> On 3/2/2012 7:19 PM, Spencer 'voogru' MacDonald wrote: >>>>> >>>>> One options is to just not allow f2p accounts. Or make them a lot more >>>>> vulnerable to votekicks/votebans. I'm considering making it so it only >>>>> takes >>>>> half as many votes against f2p to take action. >>>>> >>>>> On Mar 2, 2012 6:34 PM, "Russell Smith"<ve...@tinylittlerobots.us> >>>>> wrote: >>>>> >>>>> If you can put up with the excessive memory leaks then you can use >>>>> SourceTV on autorecord. Then just reference the time of the ban with >>>>> the >>>>> time of the recorded demo and you have yourself a demo of the supposed >>>>> cheater. >>>>> >>>>> >>>>> >>>>> On 3/2/2012 3:32 PM, Cameron Munroe wrote: >>>>>> >>>>>> Now if it only would start a demo and then ban them... >>>>> >>>>> _______________________________________________ >>>>> >>>>> >>>>> To unsubscribe, edit your list preferences, or view the list archives, >>>>> please visit: >>>>> https://list.v... >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> >>>>> 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 > > > > -- > Best regards, > AnAkIn > > _______________________________________________ > 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
