After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 406028 - gnome-terminal does not implement the DECUDK escape sequence
gnome-terminal does not implement the DECUDK escape sequence
Status: RESOLVED WONTFIX
Product: vte
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
: 143649 (view as bug list)
Depends on: vteparser
Blocks:
 
 
Reported: 2007-02-09 08:46 UTC by padraig.obriain
Modified: 2018-01-31 14:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
testcase (45 bytes, text/plain)
2007-02-09 08:49 UTC, padraig.obriain 		Details

Description padraig.obriain 2007-02-09 08:46:37 UTC 
Please describe the problem:
However, attempting to use the VT220 DECUDK escape sequence fails to create
a user-defined key and produces the error message:

  Vte-WARNING **: No handler for control sequence `device-control-string' defined.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 padraig.obriain 2007-02-09 08:49:16 UTC 
Created attachment 82210 [details]
testcase

cat'ing the attached file in a dtterm and pressing Shift+F6 causes the text 
your command here to be displayed.
Comment 2 Mariano Suárez-Alvarez 2007-02-09 19:47:56 UTC 
(Catting that to an xterm does not do anything AFAICS, either, even though xterm supposedly does implement DECUDK.)

Wouldn't this control sequence expose us to CAN-2003-0070 in another form?

In any case: vte does not implement any of the DCS control sequence. xterm's ctlseqs mentions three of these: DECUDK (User-Defined Keys), DECRQSS (Request Status String) and Request Termcap/Terminfo String (the last one is the one that gets us all the warnings about unimplemented device-control-strings, as vim is nowadays using it; this control sequence is an xterm-ism of rather recent date, I think, and would not hurt us much...)
Comment 3 Sitsofe Wheeler 2007-03-17 21:20:00 UTC 
Possibly related to bug #107031 ...
Comment 4 Christian Persch 2018-01-31 14:56:18 UTC 
This is WONTFIX since as comment 3 notes this opens the vulnerability.
Comment 5 Christian Persch 2018-01-31 14:59:03 UTC 
*** Bug 143649 has been marked as a duplicate of this bug. ***