Opinion from Community

[trevius]

What exactly are you proposing as the ideal solution, Aergad? To make everything 100% privately handled? I am sure that could be done very easily with the mini-login image wrote just by him removing the restrictions he set on it. Everything else is already in place for that.

All I am proposing is a solution that would work for everyone in almost any scenario. Sure, that would require some rewrites to the current code, but is it all that hard to change the table that it interacts with?

Also, the LSID shouldn't really matter at all. The Public LS uses it because it runs from it's own database and should always match up fine. Since it doesn't send a password to the server when an account logs in, checking the LSID should just be another way to verify that it is the correct account that is trying to connect. In the case of a private LS, you shouldn't even need to verify LSID, since you get the account and password, which should be plenty to authenticate securely with.

I am fully aware that the mini-login Image wrote uses different tables. But, since the Login Server and Server code both have the ability to be changed, anything is possible. If the issue was a limitation of the client, that would be a different story, but in this case, it isn't.

I am not trying to get anyone to do anymore work than they want to do on getting a solution created. I just wanted to mention what I consider to be the ideal permanent solution.