[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug in telnet from inetutils-2.2: Insufficient buffer space for longish
From: |
Joerg Mayer |
Subject: |
Bug in telnet from inetutils-2.2: Insufficient buffer space for longish DISPLAY names |
Date: |
Mon, 31 Jan 2022 16:23:49 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hello,
telnet from inetutils-2.2 will get stuck if a local environment variable
DISPLAY exists and and has a value longer than 44 bytes (50 -2 -4).
This is due to negotiating command 250 (X DISPLAY LOCATION) and then not
sending it because of the buffer being too small.
The attached patch tries to hack around the problem by increasing the temporary
buffer to some arbitrary larger value and gracefully fail (tested!) if even
that limit is too small.
In case you want to apply the patch as is and you regard this patch as
copyrightable material, I assign the copyright of this patch to the maintaining
organization of this software.
A non-hackish solution would probalby dynamically allocate a temp variable of
proper length.
Kind regards
Jörg
--
Joerg Mayer <jmayer@loplof.de>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
inetutils-2.2-telnet.patch
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Bug in telnet from inetutils-2.2: Insufficient buffer space for longish DISPLAY names,
Joerg Mayer <=