garoboldy
Member
- Joined
- Jan 15, 2010
- Messages
- 518
so based on the post about the recent wave:
Tripwire is only used for future logins/releases during a detection? So anything running before/during the tripwire event will be flagged.
So there's really no major need for tripwire outside of "hey there's a detection, you are flagged now" ? My understanding of tripwire was to prevent the detection and log off / lock the bot from running once any change was noticed.
Fellow Buddies,
We have been receiving a handful amount of ban reports recently. As we suspected on 21 Jan 2016 tripwire event,
accounts online during the event were flagged and they are being banned.
We would like to remind you that the detection that was captured by Tripwire on 21 Jan 2016 was the reason of May
and December banwaves. The same detection method has also flagged online accounts when the last event was raised.
As of 22 Jan 2016, said detection method is no longer a threat for Honorbuddy.
If you have received bans on accounts that were not online on 21 January or accounts that have been created after
that date, those are not caused by software detection.
There is nothing new that would require us to close auth servers and we do not need to do a new release.
Tripwire is only used for future logins/releases during a detection? So anything running before/during the tripwire event will be flagged.
So there's really no major need for tripwire outside of "hey there's a detection, you are flagged now" ? My understanding of tripwire was to prevent the detection and log off / lock the bot from running once any change was noticed.