Hacknet

Hacknet

33 hodnocení
SQL_MemCorrupt vs SQLBufferOverflow
Vytvořil: meLon
SQL_MemCurrupt vs SQLBufferOverflow
A Pointless Race With An Anti-Climactic End.

This is s speed comparison between two programs developped to hack SQL Ports in the game Hacknet.
   
Ocenit
Přidat do oblíbených
Oblíbeno
Odebrat z oblíbených
Testing Setup
So while on my way to HACK THE WORLD, I came across two .exe to hax SQL: SQL_MemCorrupt and SQLBufferOverflow. My first wonder was if one was better than the other.

To do so I needed to hack a server with a SQL port, and if that server had a tracker: I could use it to time the programs. I ended up using the /el message board server.



I Started analyzing the firewall, solved it, deconnected, started up TraceKill then connected to the server again and proceeded to overload the proxy with the tracker stuck at 100.00 as pictured above.

Once the Proxy was dealt with it was time to wip out my 1337sqlHAX.
First Test: SQL_MemCorrupt.exe


SQL_MemCorrupt:
unlocks between 77.7 and 75.3 (Excluded screens)
finishes around 73.6 (as seen above)
total RAM: 350
Second Test: SQLBufferOverflow.exe


SQLBufferOverflow
unlocks port between 78.5 and 75.9
finishes process around 74.2
RAM: 350

Ram usage being identical, the only difference is speed: We see here SQLBufferOverflow around 0.6s faster. Not much, but could make or break for some missions like the "Test of Haste".
But the difference seemed likely to be Human Error so....
Third Test: SQL_MemCorrupt.exe again


SQL_MemCorrput
Unlock Between 78.8 and 75.8
Finishes around 74.7
Conclusion / tl;dr
Half a second faster again. Human Error no doubt. Both progams seem to be equal, so if you have both get rid of one to speed things up when using auto-complete.
Both are relatively long but take less than 30 secs, and testing showed them to be close to within a second.

tl;dr:
So a pointless guide to a question that could be answered in one line: The is no difference between SQLBufferOverflow and SQL_MenCorrupt.
Počet komentářů: 6
NekoYuzu 3. dub. 2018 v 22.01 
ok,these are same file.I read them in game.
Trobby 27. čvc. 2016 v 10.43 
XD in conclusion "sql_mencorrupt"
meLon  [autor] 13. čvn. 2016 v 16.31 
@39kk9t using the tracer was just as useful, plus allowed for me to start the timer exaclty when I wanted it
"I Started analyzing the firewall, solved it, deconnected, started up TraceKill then connected to the server again and proceeded to overload the proxy with the tracker stuck at 100.00 as pictured above"
39kk9t 11. čvn. 2016 v 4.45 
Why didn't you use Clock(or Hexclock at least)?
Mx Flx 9. úno. 2016 v 14.20 
Cheers for the extra time spent making it easy to read, oh and eveyone loves pictures (:
Στυχχ 30. led. 2016 v 15.28 
aight fam.