I think I have an idea of whats causing it, will probably require a new libEQ to fix it, still looking into it tho.
Type: Posts; User: mvern
I think I have an idea of whats causing it, will probably require a new libEQ to fix it, still looking into it tho.
Just wanted to say thanks to orenwolf.
Also, wanted to point out again that my work on showeq is not dependant on any donations or anything of the sort, and I'm not actually asking for any.
If your using qt-2.x, thats likely the problem. Looks like it was broken when I changed things to get it to work with debian's qt-3.1.
No way to say for sure, one can hope, but who knows.. It seems unlikely any additional encryption added later will work the same way as the old stuff tho.
The biggest change is the removal of all the old decryption related code that was no longer used. The cvs browser is probably the best place to look to see every change, since you can pull up...
Make sure to start fresh from 'make -f Makefile.dist', etc. The configure script was updated to handle the new libEQ, and it wont work if you don't.
If it was just a "tweak", it wouldnt be a big deal. I kinda doubt they'd maintain a seperate codebase just to be sneaky with the evil seq users.
/shrug, you can probably expect a cvs commit along with the next eqgame.exe patch. Has nothing to do with payment, just no point in spending the time to fix current live code when test has different...
Its kind of funny how quickly people jump to conclusions, especialy without knowing what all is involved in fixing SEQ after an encryption or netcode change. Its not just 'fixing a few opcodes', its...
I found this site helpful when I first started playing with pthreads.
Netcode is changed a little bit on test, nothing really bad tho. Will be interesting to see if it goes live as it is now, tho.
something to do while afk on raids? :)
Actually, Ratt just set me up with access last night. :)
- mvern
patch
Added in support for the new netcode, the 'encryption' (if you can call it that :p ) and fixed a few of the main opcodes and structs.
(edited out url to avoid confusion)
If I took a guess, I'd say they probably just take a crc32 of the item's stats and use that. The server would compare the crc in the link with the real one, and if they dont match, have it fail and...
The servers has/had a little habit of sending unitialized memory in some network packets. Seeing "WINDIR=C:\WINNT" show up in the trash section of a packet more then once was enough to convince me...
The patcher uses embeded internet explorer stuff for downloads - your just seeing ie access cookie files, not really anything out of the ordinary.
cd into showeq/src and run 'patch < /path/to/test.diff'
Posted a patch here to restore SEQ to a mostly working state. I didnt get a chance to finish cleaning it up, and some of the structs are still off, but most everything is atleast working.
Some pretty major changes on test. Posting this mostly to help cut down on duplicated work. I havent worked through too much of it yet, but heres what I do know so far. Most all data is zlib...
>> SoE has already demonstraited that they are aware of the early key sniffers methods and are reacting to them.
>> The changes in the process access list show this.
The changes were made at the...
You're mistaken. Hit the search button if you want to find the previous discussion on IsDebuggerPresent
How do you figue that using debug privs is detectable, btw?
I wonder tho, since the dll actualy is running as a module in eqgame's address space, theres no violation of privacy, etc, involved in them scanning for it. Just something to consider...
The first 32 bits of the key are FFFFFFFF almost half the time. If you were to brute the key starting with that and iterating through the 4,294,967,295 possibilities for the 2nd 32 bits, you'd...