lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 17 Dec 2006 10:40:45 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Stephen Clark <Stephen.Clark@...lark.us>
cc:	Pavel Machek <pavel@....cz>, James Lockie <bjlockie@...kie.ca>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Fwd: escape key]


On Dec 16 2006 19:51, Stephen Clark wrote:
> Jan Engelhardt wrote:
>> 
>> It's something between a misdesign and a misconfiguration of the ESC key.
>> 
>> In other words, many unices make ESC generate ^[, the general
>> terminal escape character that is _also_ generated by keys like "up",
>> ^[[A.
>> 
>
> do man ascii - ESC is 0x1b.
> Thats what the esc key should generate - it sometimes echoed as ^[ because the
> [ = 0x5b

Ok I hoped people would be smart enough to figure, but let me rephrase in two
ways:

  Many unices generate "\x1b" (^[) for ESC, which is also generated by
  keys like "up", which generates "\x1b[A" (^[[A)

>> MS-DOS, or rather QBASIC's, Turbo BASIC's and other implementation of
>> keys, does not have this "bug": here ESC generates "\x1B" and "up"
>> generates "\x00H" IIRC. There is no key defined to generate "\x00".
>> => All fits nicely.

  And QB generates "\x1b" (^[) while "up" generates "\x00H" (^@H).


Hope this makes things more clear - I interchangably used the ^ and the \
notation. Sorry if that confused anyone.

	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists