- UID
- 106609
- 帖子
- 130
- 主題
- 9
- 精華
- 0
- 積分
- 11
- 楓幣
- 307
- 威望
- 9
- 存款
- 0
- 贊助金額
- 0
- 推廣
- 0
- GP
- 14
- 閱讀權限
- 10
- 性別
- 保密
- 在線時間
- 32 小時
- 註冊時間
- 2015-7-16
- 最後登入
- 2021-12-26
|
本帖最後由 Missing 於 2015-11-15 11:26 編輯
LS管理員iMeh 已更新一大後說話
內容大致如下:
Dear Community,
First of all, we would like to apologize for the delay of our investigation. We sincerely thank you for your patience. We understand that a large part of our userbase is disappointed because of the lack of transparency and status updates. However, we can ensure you that it was the right decision when it comes to playing in the hands of Riot Games. Therefore, we cannot divulge too much information, because it may be used against us by Riot.
親愛的各位L#用戶,
首先,我們要對我們延遲/延後 我們對banwave和被偵測的調查而作出道歉, 我們衷心的感謝大家的耐心和配合 據我們了解到, 在L#的用戶和使用因為我們欠缺透明度(欠缺及時的解釋和更新l#安全性狀態)而對我們感到非常失望. 但是, 我們可以好肯定的告訴你, 這是一個正確的決定,因為當你們在玩lol的時候, 如果我們透露更多關於防封/防偵測內容的話, 這會成為Riot 針對我們的行動作出更加多的防封手法, 這樣就會令我們當使用L#的時候被陷於Riot的五指山之中,無法逃脫.
Situation
Over the past weeks, all previous League of Legends binaries have been re-checked for anything out of the ordinary. We have thoroughly checked the entire way LeagueSharp interacts with the League of Legends game servers. This is why the investigation took as long as it did. We are really sorry for any banned users that were affected, but please keep in mind that it is a penguin and fish game -- there is always a chance to get banned. We can't stress enough to refrain from cheating on accounts that you cannot afford to lose.
情況/狀況
在過去的幾個星期裡, 以前所有LOL裡面的二進位的文件已被重新檢測為不正常的.我們已經徹底地檢查所有LS跟LOL裡面所回傳給伺服器的數據和文件.這是確實存在所以我們為什麼要花那麼多時間下去調查這件事情.我們對因為所有被封號潮影響的用家感到非常抱歉, 但請你們記住,這是一個貓抓老鼠的遊戲, 老鼠總會有被抓到的一天,即代表永遠沒有可能有一定不會被封號的機會. 我們不能去欺騙大家使用L#後能避免不會被封號的可能性和損失.
Findings
We noticed that a few things were not working as they should and we re-worked a large amount of code of LeagueSharp to make sure that everything fits our safety standards again. Note here that these flaws still exist in any other tools interacting with League of Legends. As far as we know, the actual injection is safe (where LeagueSharp connects to your game). We must emphasize that safety cannot be 100% guaranteed, but we will continue trying our best to reach the highest level possible. In the previous patches, several measures were taken to make the usage of LeagueSharp more safe. For example, by implementing a global humanizer in the core and randomizing everything around LeagueSharp itself, along with some other things that affect the way LeagueSharp interacts with the game servers. There is evidence to suggest that Riot Games started analyzing the network traffic and gave up fighting in the memory.
暫時找出的調查結果
我們注意和發現到, 我們有些事情(防止被RIOT偵測)的方法並沒有起到作用(應該是5.20BANWAVE之後). 我們在這之後應該針對LS重新編制大量的代碼.以確保我們以前所承諾的安全標準的準則,這也是我們開發L#所作出的承諾.要注意的是,這些程序中的缺陷仍然跟L#和其他輔助軟件(BOL,zeroedOS等等)存在, 簡單一點,就是各種輔助也不能完全倖免.據我們了解, 使用LS注入遊戲是安全的(當LS注入到遊戲當中),但我們必須澄清這也不是100%安全的,但我們會盡我們最大的努力去做好以後的工作和安全水平. 在前幾次LS的更新中,我們已經使用了幾種措施去令使用LS的用戶的安全性提高. 例如通過使用HUMANIZER和LS CORE的配合, 而令大家的帳號安全一點.連帶影響LOLCLIENT 回傳給伺服器數據的方法. 但這也有證據證實和表明, RIOT已經使用了網路流量去監測玩家是否使用外掛, 而且放棄使用偵測內存(檢測隱藏程序)的方法去檢測外掛.
Future
As you may have noticed, we have been pushing many core updates more frequently than ever before. These are all to modify LeagueSharp, such as "anti- anti-cheat" measures (this is just as a precaution), and other security features. Riot has worked to make it unclear when the bans will stop, which is typical in this penguin and fish game. We are still working on a more final and permanent solution to the server-sided detection issue. We believe that the bans will reduce in the next few weeks and that the only bans left would be ones that are delayed or flagged. Therefore, we hope that we have already found and fixed the issue. We recommend that you only script on smurfs, or accounts that you do not care about as much. Currently, it is just a matter of time until we know the future of LeagueSharp in relation to Riot. Please also keep in mind that every other cheat tool provider is being affected by bans because of the server-sided detection. However, it is not simply the tools, but the entire act of scripting. Overall, scripting in general is detected, not the tool. We do not know for certain what exactly is "detected" by Riot on the server-side. The majority of scripters and cheaters are still continuing to play without any bans. Only time will tell.
未來及展望
正如你們可能已經注意到,我們比以前比起來更新CORE的頻率是更高, 例如反編釋LOL的內核程划,以及其他L#的安全性問題,我們已有比以前更多的頻率去更新這些東西,我們仍然去努力解決雙向回傳數據和防止被偵測的問題. 我們建議大家暫時在未解決真正問題的幾個星期內,使用小號去使用LS,或者是不用那麼多明顯的腳本, 這也是我們早已會預料到的問題,這些事情也跟其他第三防軟件有密切的關係,不是只針對LS來做的,我們到現在也不太清楚RIOT的真正檢測方法, 而他們檢測到的是腳本而不是LS本身這個工具, 我相信各個用戶和腳本作者也非常努力去解決問題, 最後, 時間會給出答案的.
By 翻譯:clavin3ivan
現在因該每一家都有這次封波、
這三次更新來看GGC這次更加防範外掛。
BOL、GOS、EB 都有被鎖
意味著LOL會增加了ANTI-CHEAT
- L# 注入是安全的
- 有證據顯示,Riot 已放棄從本機抓外掛,改從伺服器端分析玩家的網路流量,所以任一款外掛都可能被偵測到
- 目前還不清楚 Riot 在伺服器端動了什麼手腳,雖然 L# 已經陸續進行不少安全性更新,還是請大家斟酌使用!
|
|