[devn00b]

Originally Posted by Eglin

Don't be a moron.

how is that moronic? he happens to know me well enough to know that there is no way in hell that i would release my database. Only 3 people have the real db. his comment stands. and you just mad an ass of yerself. grats.

It is a reasonable request. When I get back on broadband, I will write an opensource login server (if I still have any interest in eq/eqemu). I don't see any reason for withholding the source to it, and I think that all of the reasons I've seen so far are just retarded.

and who are you to sit and judge? you did some nice work with perl scripting, i'll give you that. but to sit and call the rules retarded because it doesnt benifit you or the others is moronic. you dont like it? make yer own please.

I remember reading in Mirth's RE post that he could already generate packets when trying to figure out the format... that probably means that the login server was derived by reverse engineering the dll that ships (shipped?) with ethernalquest. That is probably where I'd start, at least (or did SEQ hack the login sequence, too?). Whatever the case, duplicating minilogin-level functionality would probably not be too hard.

Please dont post things you have nfi what you are speaking of. The above text is incorrect 100%.

As to why the loginserver code is so jealously guarded... Maybe the eqclient does some things it isn't supposed to, like report system information or modify files or expose some command interface that it shouldn't... It won't run w/o sysadmin privs, so it is entirely possible. Since sony tech support will basically tell you to disable your firewall if you want to play, security and privacy are obviously not their top concerns. At the very least, I'd imagine that cd keys are transmitted as part of the login process. It would make sense that you would want to be able to ban users in some way - cd keys seem like the most reasonable way to do so. Where jealously guarding code that would enable login password snooping seems silly to me, trying to protect cd keys makes a little more sense. The only other possibility I can think of is that it is held secret in hopes of preventing SOE's legal wrath. As it is, SOE has only to kill the loginserver for all of eqemu to die (unless some renegade dev like me writes an opensource version).

Okay loginserver is closed source, is now always will be. We dont owe anyone an explanation as to why its guarded it just is. dont like it feel free not to use eqemu.

I can't imagine running a public server where _my_ users would still have to register w/ EQEmu. Why should they? What if I have a falling out w/ the EQEmu project or branch the code? Do I want to have to still be subject to using their login server? I don't think so. Since the world/zone servers are gpl, a branch is a very real possibility. As far as splintering the user-base... I don't see any reason that loginservers couldn't pass information from one to another. Nor am I aware of anything that would prevent modifying world servers to register with multiple login servers. So, while the official stance is that minilogin is not and never will be open source, I think that you can still rest assured that there will eventually be an open source login server.

im not even going to respond to this last blurb. elgin, as i said above grats on adding perl to eqemu thank you whatever. But dont make statements when you have less than no fucking clue why we do what we do.