29 Apr, 2010, Kline wrote in the 1st comment:
Votes: 0
Does anybody else experience this? It happens to me every 3-4 weeks or so; I change my MUD name by a character so I can reconnect to the network then when it kills that name I change back to the original…Back and forth, etc. Nothing ground breaking, just annoying, and it has my curious what the cause could be.

Existing MUD name that ceased to work…

[ IMC] Invalid authentication response received from authentication!!
[ IMC] Data received: SHA-256 authentication is required.
[ IMC] Shutting down network.

After rename on initial connect…

[ IMC] Autosetup completed successfully.
[ IMC] SHA-256 Authentication has been enabled.
[ IMC] Connected to Server02. Network ID: MudBytes
29 Apr, 2010, Kardon wrote in the 2nd comment:
Votes: 0
It sounds like your MUD is enabling SHA256 encryption for passwords in your autosetup packet, however on subsequent connections you are still trying to authenticate in plain text and the server is expecting an SHA256-AUTH-REQ to start your MUD's authentication. Does this tend to happen after you reboot your MUD?

Hope this gets you pointed in the right direction.
30 Apr, 2010, kiasyn wrote in the 3rd comment:
Votes: 0
your client would either not be using sha256 or requiring the server to use sha256.

play with the 'imcconfig sha256' and imcconfig sha256pass commands
30 Apr, 2010, quixadhal wrote in the 4th comment:
Votes: 0
Funny, I just started getting this on WileyMUD, which I can guarentee has not changed any config info for about 6 months. :)
I do indeed use SHA authentication, and to fix it I had to comment out the SHA256Pwd line so it would reset. For some reason, the value was "1", which probably isn't valid?
30 Apr, 2010, Kline wrote in the 5th comment:
Votes: 0
I'm using the Freedom Client provided from here, and again, this only happens every few weeks. Once I get the game connected I haven't ever touched the config data except to rename my MUD so I can reconnect once the server stops liking me.

I'll start looking at this where quix did after I get to my hotel tonight. Thanks.
30 Apr, 2010, Davion wrote in the 6th comment:
Votes: 0
If you set SHA256 to 1, and SHA256Pwd to 1, it should be fine. That's what I use and I've never had this problem.
30 Apr, 2010, Kayle wrote in the 7th comment:
Votes: 0
If this was one person having this issue, I'd say client issue. But since two people are having the issue, and it works fine for a week or so and then out of the blue stops working without them changing something.. Something is wrong with the Servers.
30 Apr, 2010, ATT_Turan wrote in the 8th comment:
Votes: 0
It also happens to me - I log in infrequently, so I can't say whether it's every few weeks or something more or less regular than that, but at least twice since I've gotten myself configured properly for IMC I've had to toggle the SHA256pass option back and forth to get the MUD to connect to the server.
30 Apr, 2010, quixadhal wrote in the 9th comment:
Votes: 0
If it is a server issue, it's probably only affecting code derived from the Freedom Client. My game also uses that, albeit I had to bash it with a large stick to get it to work (Diku Alfa + 10 years of drift). :)

An LpMUD (Dead Souls 3 mudlib, FluffOS driver) connects to the same port from the same machine with no issues. It probably doesn't use SHA256.

I suspect the issue may have to do with re-authenticating, as my Diku doesn't reboot every day as many of them do, so it may only have a shot at developing the problem every few weeks (whenever I muck with my firewall, basically).
01 May, 2010, kiasyn wrote in the 10th comment:
Votes: 0
sha256 means 'please negotiate sha256 passwords only' and sha256pwd means 'we've negotiated sha256 passwords, only use them from now on'
01 May, 2010, kiasyn wrote in the 11th comment:
Votes: 0
I'm guessing what happens is MUDs that are logged in for a long time eventually get flagged as 'unused' and wiped from the list. I'll look into this.
03 May, 2010, Kline wrote in the 12th comment:
Votes: 0
kiasyn said:
I'm guessing what happens is MUDs that are logged in for a long time eventually get flagged as 'unused' and wiped from the list. I'll look into this.


Thanks. I didn't get a chance to look at this over the weekend from my end as I had hoped; too busy. This may be the issue since my MUD rarely disconnects. It runs from my home line (very stable) and is setup to send keepalive packets to ensure the link stays up. Let me know if you need any info from my side and I'll provide what I can.
04 May, 2010, ATT_Turan wrote in the 13th comment:
Votes: 0
Kline said:
kiasyn said:
I'm guessing what happens is MUDs that are logged in for a long time eventually get flagged as 'unused' and wiped from the list. I'll look into this.


Thanks. I didn't get a chance to look at this over the weekend from my end as I had hoped; too busy. This may be the issue since my MUD rarely disconnects. It runs from my home line (very stable) and is setup to send keepalive packets to ensure the link stays up. Let me know if you need any info from my side and I'll provide what I can.


Ditto (not run from home, but very long uptimes).
0.0/13