Source code for Minilogin
 

Can someone point me to the location of the Minilogin source code. I want to add some functionality to it to allow multiple user ID logins and to utilize the accounts file.

Regards,

Minilogin source has never , is not , and never will be open source.

Why is that???
 

I guess my question is why not? What make this piece of code different from the all the other source code???? It's unsupported code and there is much potential for improvements within it. If you ask for an improvement you get the "That unsupported".... Well, If thats the case why not let delevopers out there tweek the code for thier own needs, Why hide the source???

Makes no sense to me!!! :?

We have a very good reason to hide the source for a login server: encrypted passwords.

Same reason the loginserver code is not released.

There is no need for your seperate loginserver anyways unless you are trying to prove that you made the emulator yourself. Just use the EQEMu loginserver and you'll be fine.

And if you're trying to setup a lanserver, then you're obviously missing some key points.

Just looking at my own copy of the login server gives me a warm fuzzy feeling inside.
Now to go off and practive the secret handshake...

heh too bad thats outdated and it doesnt include the crypto that you need to be able to use it :)

Yeah I know. I've got no idea why I kept it.
Lets just call it novelty value

Sure there's a need. My wife and I both want to play on our own server. We're not interested in setting up a server that can be seen by the outside world, in fact, it wouldn't matter if the outside world COULD see it as we have Charter for an ISP and they don't allow servers. However, the way my LAN is set up, I can't go through the EQEMu login servers to play. My Linux box, the one that runs the server, is also my gateway. If I set up the server to work on the external IP address (which I'd have to do to connect to the EQEMu login servers), I can't connect from my LAN. If I set it up to use Minilogin, I can only connect one account at a time. I seem to remember a long time ago when MiniLogin would allow up to 16 connections at once, which even that would be overkill. If I had a MiniLogin that allowed even just 2 connections at once, I'd be able to do what I want to. As it is, I can't, and I guess I won't be able to.

I run 4.4 and 5.0 with minilogin and i can have more then 1 account on at one time, i have had all 3 of my computers on it at once. My best guess would be its a set up issue not a minilogin issue.

There's supposed to be a MiniLoginAccounts.ini which specifies which IPs use which accounts in a format like IP name password.

Although upon trying this myself, I receive this output of minilogin:

LoginServer.ini read.
Error in MiniLoginConfig.ini on line #1: Invalid format, should be 'IP username
password'
MiniLoginAccounts.ini read.
Server mode: Standalone
Login server listening on port:5999

While both my .ini's look like:

127.0.0.1 name pass

A quick search shows no answers on the solution for this yet, but Mattmeck, you suggested there's a weird character seperation in this post.

Edit: Seperating the fields with the space character from ALT+0160 seems to get rid of the error message with minilogin, though despite my having defined 127.0.0.1 and my external IP to be a non-eqemu account, world.exe still reports that account connecting. Does Minilogin 5.0 still support multiple accounts? Perhaps the primary machine running minilogin always logs in as 'eqemu' and others are able to be specified?

Another edit: This was answered here and thus far appears to work rather well.

I was wondering, could the encryption and decryption routines be made into pre-compiled DLLs?
That way, the minilogin source can be released or at least an API whitepaper
so someone can make a graphical client?
Maybe a graphical client will let you be able to monitor connections on the fly, kick users etc...

Just a thought =)

Chrysm you know that people can crack DLLs, we already have a DLL but it has more features than just the loginserver crypt plus only two people have the source to the DLL.

An idea would be more to source it with the encryption routines pre-compiled into DLLs, BUT have eqemu's general login server encryption different than the one that's released. Meaning having a more generic encryption routine for the general public's download.
Granted that would make private servers in this case less secure, but if there's no public showing for it, wouldn't it be pointless to be more secure?
I'd find it a trade off in that case, you can have your own login, but it's not as secure as the one that eqemu runs.

How would that work ? As I understand it, the login server needs to decrypt the password that the EQ client encrypts. To have a different encryption algorithm would require altering the client, no ? (or just ignore the password, as I think minilogin does)