- 精华
- 0
- 帖子
- 267
- 威望
- 0 点
- 积分
- 267 点
- 种子
- 0 点
- 注册时间
- 2009-6-9
- 最后登录
- 2012-12-10
|
Sammy Lt on the way, no ETA. JF Team adding our key vertification routines.
Recently, c4eva contacted us with a proposal for a key verification procedure.
Basically, with known key to hand you can check it against a connected drive. These procedures have always been been there, but now we can use them to our advantage. They are clearly visible in C4eva’s live logs.
OK…. So we messed with the routines for a few hours as per C4eva’s instructions and with a bit of to-ing and fro-ing, we got them to work.
As for a known key, you should have them in your database.
So we are adding a couple of routines.
1. Simply bang every key you have at the drive until it hits the right one…. Simples! It does a hundred keys in a couple of seconds…. Brutal, but effective.
2. Lite-on have a unique identifier in their Inquiry. So, on a port refresh, a lite-on can be readily identified and the key returned and verified – Uber Cool -
3. So we are adding an index to the KeyDB against the drive barcode, to take advantage of 2 above. KeyDB refreshes will also update existing entries..
The team are testing an bashing around ideas on what to do once you have the key…….
不知所云
好像是更严密的防ban,
严密 <>完全
是不是又要大ban了。。。。. |
|