From jhawk@MIT.EDU Sun Oct 6 16:49:31 1996
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id QAA05130 for <bugs@RT-11.MIT.EDU>; Sun, 6 Oct 1996 16:49:30 -0400
Received: from LOLA-GRANOLA.MIT.EDU by MIT.EDU with SMTP
id AA00679; Sun, 6 Oct 96 16:49:17 EDT
Received: (from jhawk@localhost) by lola-granola.MIT.EDU (8.6.12/8.6.12) id QAA24727; Sun, 6 Oct 1996 16:49:16 -0400
Message-Id: <199610062049.QAA24727@lola-granola.MIT.EDU>
Date: Sun, 6 Oct 1996 16:49:16 -0400
From: John Hawkinson <jhawk@bbnplanet.com>
To: krb5-bugs@MIT.EDU
Subject: global and "open" subcommand argument parsing is inconsistent
Architecture: sun4
Telnet syntax parsing for the "open" command is inconsistent with
the global syntax parsing.
For instance, all three of these work:
telnet -a hostname telnet telnet -a
HOWEVER:
telnet -al username
fails. Nevertheless, these work:
telnet -al username hostname telnet
This doesn't make sense. It's inconsistent. Note that the usage messages
are:
Usage: telnet [-8] [-E] [-K] [-L] [-X atype] [-a] [-d] [-e char] [-k realm]
[-l user] [-f/-F] [-n tracefile] [-r] [-x] [host-name [port]]
and
usage: open [-l user] [-a] host-name [port]
In addition, there are global options that would make sent to "open".
Also, there is some duplication with the command-line argument space
and the "set foo" space.
See above.
I don't know.
Eichin suggests that allowing:
telnet -a
to work is incorrect, but can't offer good reasoning to suppor that.
Personally, I'm used to
telnet -ax
and would like that to continue to work. I think I'd want to see
-options removed from the open subcommand (or deprecated) in favor
of the model where -options to the command line set variables
which are modifyable though "set foo" syntax.
This is not a big deal...
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id QAA05130 for <bugs@RT-11.MIT.EDU>; Sun, 6 Oct 1996 16:49:30 -0400
Received: from LOLA-GRANOLA.MIT.EDU by MIT.EDU with SMTP
id AA00679; Sun, 6 Oct 96 16:49:17 EDT
Received: (from jhawk@localhost) by lola-granola.MIT.EDU (8.6.12/8.6.12) id QAA24727; Sun, 6 Oct 1996 16:49:16 -0400
Message-Id: <199610062049.QAA24727@lola-granola.MIT.EDU>
Date: Sun, 6 Oct 1996 16:49:16 -0400
From: John Hawkinson <jhawk@bbnplanet.com>
To: krb5-bugs@MIT.EDU
Subject: global and "open" subcommand argument parsing is inconsistent
Show quoted text
>Number: 73
>Category: telnet
>Synopsis: global and "open" subcommand argument parsing is inconsistent
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: hartmans
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Sun Oct e 16:50:00 EDT 1996
>Last-Modified: Thu Sep 13 21:34:43 EDT 2001
>Originator: John Hawkinson
>Organization:
BBN Planet>Category: telnet
>Synopsis: global and "open" subcommand argument parsing is inconsistent
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: hartmans
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Sun Oct e 16:50:00 EDT 1996
>Last-Modified: Thu Sep 13 21:34:43 EDT 2001
>Originator: John Hawkinson
>Organization:
Show quoted text
>Release: beta-7
>Environment:
System: SunOS all-purpo 4.1.4 4 sun4m>Environment:
Architecture: sun4
Show quoted text
>Description:
Telnet syntax parsing for the "open" command is inconsistent with
the global syntax parsing.
For instance, all three of these work:
telnet -a hostname telnet telnet -a
Show quoted text
telnet> open -a hostname telnet> open hostname
HOWEVER:
telnet -al username
Show quoted text
telnet> open hostname
fails. Nevertheless, these work:
telnet -al username hostname telnet
Show quoted text
telnet> open -al username hostname
This doesn't make sense. It's inconsistent. Note that the usage messages
are:
Usage: telnet [-8] [-E] [-K] [-L] [-X atype] [-a] [-d] [-e char] [-k realm]
[-l user] [-f/-F] [-n tracefile] [-r] [-x] [host-name [port]]
and
usage: open [-l user] [-a] host-name [port]
In addition, there are global options that would make sent to "open".
Also, there is some duplication with the command-line argument space
and the "set foo" space.
Show quoted text
>How-To-Repeat:
See above.
Show quoted text
>Fix:
I don't know.
Eichin suggests that allowing:
telnet -a
Show quoted text
telnet> open hostname
to work is incorrect, but can't offer good reasoning to suppor that.
Personally, I'm used to
telnet -ax
Show quoted text
telnet> open hostname
and would like that to continue to work. I think I'd want to see
-options removed from the open subcommand (or deprecated) in favor
of the model where -options to the command line set variables
which are modifyable though "set foo" syntax.
This is not a big deal...
Show quoted text
>Audit-Trail:
>Unformatted:
>Unformatted: