← Back to team overview

mudlet-makers team mailing list archive

[Bug 1674601] Re: Mudlet or game output hangs with crafted input

 

Well, is there ASCII ESC characters in there or not - they would not be
visible in a copy and paste to, say here and they were entered as a
literal in a Mudlet Lua code/script in the editor they would not be
saved correctly IIRC.

Actually, reading between the lines it is almost as if telnet echo
(suboption 1) has been set incorrectly somewhere - IIRC we do not ever
allow it to be turned off on our end - which is broken for log
files/replays where the server has told us not to echo but we still do
and thus stick passwords that we send and then get echoed back stored in
the buffer/logs. Given that, is it possible that something in that
combination is being interpreted as telling the server NOT to echo what
we expect it to?

I may have this totally wrong - I will really have to get my head around
telnet option negotiation someday. 8-(

As to being able to mess with the command separator - sometimes you DO
need to send the separator character to the MUD - like in this case
where it is required for what looks like an ANSI ESC code - so how do we
get around that?

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1674601

Title:
  Mudlet or game output hangs with crafted input

Status in Mudlet:
  Confirmed

Bug description:
  Steps to reproduce:

  * ensure your command separator is set to ;
  * connect to an IRE game like Lusternia.com and log in
  * do: lua display((Polaris): You say, "Test.")

  What happens: any input you enter is not reflected by the game. Mudlet
  still sends the input (confirmed by Wireshark) and Mudlet still
  receives output from the game (confirmed with ambient effects still
  showing).

  It makes it really hard to tell if it's Mudlet or the MUD with the
  issue since Mudlet is still sending and receiving data as far as I
  see.

  Reported by Pharanyx on Discord.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1674601/+subscriptions


References