Quote:
Originally Posted by image
To add: DLL's are linked to exes so someone could take the DLL and make it into a DLL useable by a packetcollector, get the idea?
|
Yes
Quote:
Do not try to argue that statement because they have the DLL on their computer and any modifying that needs to be done to the DLL they can and will do.
|
Don't want to argue.
I just wanted to state what I was thinking. Someone makes an open source login for example, as a basic framework with functionality of little things like checking ip's etc etc.
In the source code would be a blank function to encrypt and decrypt whatever and it's left blank. Then the source is submitted for approval to the EQEMu team to overlook it and if it's deemed ok to use, the dev team inserts the functions and then releases the binary. No one other than the devs would still have access the the secret information but, other people who want to help could make the basic program for approval.
That was my line of thinking on that part. I know you guys are right and the encryption/decryption routines shouldn't be given out.
Secondly, I thought as far as DLLs go, it's basically a header file with functions in it, and you just call those functions to do what you want. Am I wrong in that assumption? I know shit about how windows works.
PS-THIS IS NOT AN ARGUMENT I just want to discuss some ideas and stuff. It is by no means to cause trouble or anything, just to learn. Just in this post, I have learned the overview and I guess it helps with having a better understanding of the entire structure.