You do know that md5 is one way right? Once it's encrypted there's no going back.

The problem with that is that if they sniff packets they can pull out the md5, and even though they can't get it back out, they can send it already hashed. Of course, we could defeat that with a salt, but SSL would still be far more secure.

I say, as long as it's compatible and secure, the method does not matter to me. :D

FYI: We used DES3 with our software, though I had nothing to do with that part of our projects.

No, don't try to make the client hash the password before sending it up. Send the password encrypted, but using something that can be decrypted. SSL would be perfect because the keys are dynamically generated, and the server would be able to decrypt the block once it got it. Then, using the (now decrypted and now plaintext) password, the server compares a hash of it to the hash you have in the user database, to see if the password is correct.

That sounds like it would work. I do have one question though, well a few. First, who on here actually runs the EQEmu LS? And second question, what is not secure about the code in it that disallows it's distribution, or is the EQEmu LS code not compiled code? I know that the recent but currently defunct Minilogin was written in Perl, and I do know of utilities out there that compile Perl code into a standalone executeable.

hmm, i'm not sure about the 'defunct' world. i admit it's getting old, and does not speak loud, but it can still be used afaik. Technical reasons prevent me from really working on it at the moment though.

Ack, sorry smogo didn't mean it like it came out. It does work well.. for 5.7DR6. I meant that it is not compatible with 5.8/9. Sorry about that! From a technical perspective, what is it that is keeping you from being able to update ML? Did Sony change something in the handshake that can't be simply updated?

np. No there's no impossible thing to update, it's just not scheduled yet ;)

Doodman make LS, LE host it (i think, correct me if im wrong)

There are a lots of topics about this subject, nothing really prevent them to release it, they just dont want to, its their choice,.

I wouldnt say defunct, neither old, but yes, on some points, you are right, Minilogin is no more compatible EQLive.

First, few peoples have the skills required to work on a LoginServer, this make only 1 months now we are working on "World of Alkora" one. Basically, "World of Alkora" server is meant to run our server which is on 5.7DR6, and we decided to release the source to allow other peoples to become independant from EQEmu LS. Now, what retain us from going to live ? Well, our vision is rather different than EQEmu one, our server is under development, and catching live is far from being a priority, mainly because we have a tons of things to dvelop. We are actually converting our PERL LS to C++, to allow more people to work and improving it, making it opensource LS. With all the hands on EQEmu, im sure we can all work together to make a valuable LS that can quickly catch up live.

<3

Awesome guys, thanks for the updates. There's no rush really as long as EQEmu LS stays active. My only real concern is being able to still run my server if (god forbid) something should happen to the official EQEmu one. I also like the fact that it's being converted from Perl to C++ as it is more widely known and there will be more people able to contribute to it's development.

Hi all, I really would appreciate any help...i am getting the next problem with minilogin, i am using WoA backpacht then i guess that my client version is correct, i have tried 7-31 , 6-16 and 6-21 servers (all are 5.7-DR 6) and i am getting always the same error, i get to server selection screen, i push play Everquest, then i get back to login account screen... This is the mini.log file that i get using: perl -w minilogin.pl > mini.log

reading : 127.0.0.1 eqemu3 eqemu3
setting 0 to id 591, eqemu3 / eqemu3
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
currently on :
new incomming server ...
key : 127.0.0.1:1032
key : 127.0.0.1:1032
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : Arex's revenge
World key : 127.0.0.1:1032
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 127.0.0.1:1037
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 03 00
opcode 1 , sequence id 0
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 40 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 00 20 00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 33 00 65 71 65 6d 75 33 00 00 00
in reply to seq # 0
leading block
leading block
in reply to seq # 0
message in packet is :
00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 33 00 65 71 65 6d 75 33 00 00 00
opcode 2 , sequence id 1
message type 0009 0001, answer with ... ack
login = eqemu3 eqemu3
login : eqemu3
pass : eqemu3
login match : eqemu3 ( eqemu3,eqemu3)
client id is : 1
auth key : ER1lb3TdJ
sending login key informaion
aknowledging seq id 1 to client (pure ack)
client authentified
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 24 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 01 10 00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
in reply to seq # 1
leading block
leading block
in reply to seq # 1
message in packet is :
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1032 : Arex's revenge
4950554648464846490
sending info for 1 servers, total 47 bytes
127.0.0.1:1032
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 16 bytes, message type : 0x09 retry count : 0x02
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1032 : Arex's revenge
4950554648464846490
sending info for 1 servers, total 47 bytes
127.0.0.1:1032
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 4 bytes, message type : 0x15 retry count

I also am having the same problems as several people in this thread: I run minilogin.pl, world.exe, boot5zones.bat and all seems fine. Then I login to the server select screen (after it tells me that there have been 1.4 BILLION failed login attempts since my last login, if that tells you anything). I select my server from the list, click play eq, and am promptly dumped back to the login screen.

I'm running a 5.7 DR6 server and am able to login and play just fine on other 5.7 DR6 servers.

For the record, the server is running on 192.168.0.2 and I'm trying to login from 192.168.0.1.

Configuration files:

miniloginaccounts.ini: (in directory with minilogin.pl)
db.ini: (no spaces at end of lines)
loginserver.ini:
Output from minilogin.pl: (from initial run to after client gets booted)

Thanks in advance for any help! Anyone have an ideas as to what the problem might be?

@mystic :
if you still get the pb, it seems the server gets contacted by the client, and kicks it right away because ... something

Now check your logs.world.log file in the EQEMu server directory. You might read something about 'Bad/Expired key'. Can youconfirm that ?

@camaris :
might be same pb. Checkout your output from the world server (world.exe), it will tell if client tries to connect (what i believe, as you get actively kicked)

I have checked that mistyc and me are getting problems with sequence id 4, and it dont get sequence 5 and 6. And i neither am sure if opcodes are really correct. Any help would be very appreciate....

I am using now a name and password in DB, because i am using minilogin (not ls) then i ll past here my new minilogin.log and world.log, and i also get this warnings:

Name "main::socket" used only once: possible typo at minilogin.pl line 118.
Useless use of a constant in void context at world.pl line 183.



WORLD.EXE (log):

[Status] CURRENT_WORLD_VERSION:EQEMu 0.5.7-DR6
[Status] Loading variables..
[Status] Loading zones..
[Status] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=34229, max id=77505
[Status] ./LoginServer.ini read.
[Status] Loading guild ranks..
[Status] Loading ./addon.ini..
[Status] Loading EQ time of day..
[Status] Deleted 0 stale player corpses from database
[Status] Deleted 0 stale player backups from database
Warning: You need to get laid...
TCP listening on: 127.0.0.1:9000
World server listening on: 127.0.0.1:9000
Connected to LoginServer: 127.0.0.1:5996
60778 New TCP connection: 127.0.0.1:1043
New zoneserver: #1 127.0.0.1:1043
Zoneserver SetConnectInfo: 127.0.0.1:1043: 127.0.0.1:7996
60848 New TCP connection: 127.0.0.1:1044
New zoneserver: #2 127.0.0.1:1044
Zoneserver SetConnectInfo: 127.0.0.1:1044: 127.0.0.1:7995


MINILOGIN.PL (log)
reading : 127.0.0.1 eqemu eqemu
setting 0 to id 591, eqemu / eqemu
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
new incomming server ...
key : 127.0.0.1:1054
key : 127.0.0.1:1054
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : World of Norrath
World key : 127.0.0.1:1054
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1054 : World of Norrath
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1054 : World of Norrath
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 127.0.0.1:1059
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 03 00
opcode 1 , sequence id 0
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 38 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 00 1e 00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 00 65 71 65 6d 75 00 00 00
in reply to seq # 0
leading block
leading block
in reply to seq # 0
message in packet is :
00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 00 65 71 65 6d 75 00 00 00
opcode 2 , sequence id 1
message type 0009 0001, answer with ... ack
login = eqemu eqemu
login : eqemu
pass : eqemu
login match : eqemu ( eqemu,eqemu)
client id is : 1
auth key : FwrPYbXVm
sending login key informaion
aknowledging seq id 1 to client (pure ack)
client authentified
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 24 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 01 10 00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
in reply to seq # 1
leading block
leading block
in reply to seq # 1
message in packet is :
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1054 : World of Norrath
4950554648464846490
sending info for 1 servers, total 49 bytes
127.0.0.1:1054
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 20 bytes, message type : 0x09 retry count : 0x03
00 09 00 03 0d 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
opcode 13 , sequence id 3
request to contact server # 0
aknowledging seq id 3 to client (pure ack)
connecting to server : 127.0.0.1:1054,
client id : 1
name eqemu
CLE FwrPYbXVm (0, 0)
packet pending in out queue, length : 71
packet for tcp transfer is : 71 long
2 16 71 0 1 0 0 0 101 113 101 109 117 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 70 119 114 80 89 98 88 86 109 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
sending packet to tcp socket ... transmitted
)key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 4 bytes, message type : 0x15 retry count : 0x03
00 15 00 03
message type 0x15, packet # 3 received and acknowledged by client
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 16 bytes, message type : 0x09 retry count : 0x04
00 09 00 04 03 00 05 00 00 00 00 00 00 00 00 00
opcode 3 , sequence id 4
message opcode 0004, answer with type??

hi,

minilogin works not too bad afaik (we use it eeveryday for development purpose). However some of you had problems connecting.

It seems it happens on localhost ips (127.0.0.1) mostly (if not only, though i can't imagine the reason). Has anyone had success using 127.0.0.1 ?

If so, can you describe what config files you are using, and how you got it to work (i can't test this because i run server on linux only)

Thank you for contribution.

My config files :