Newsgroups: comp.dcom.sys.cisco Path: utzoo!utgpu!cunews!bnrgate!bcars223!fortinp From: fortinp@bcars223.bnr.ca (Pierre Fortin) Subject: Re: Feature/bug in password handling Message-ID: <1990Sep11.072124.28692@bnrgate.bnr.ca> Sender: news@bnrgate.bnr.ca (USENET News System) Organization: Bell-Northern Research, Ltd. Ottawa Ontario CANADA References: <25934@boulder.Colorado.EDU> <1990Sep10.200259.400@ico.isc.com> Date: Tue, 11 Sep 90 07:21:24 GMT In article <1990Sep10.200259.400@ico.isc.com>, dougm@ico.isc.com (Doug McCallum) writes: > In article <25934@boulder.Colorado.EDU> HANK@TAUNIVM.BITNET (Hank Nussbacher) writes: > >I am not sure if this a feature or a bug, but the cisco configure processor > >preserves trailing blanks. This causes the nasty problem of a password > >typed in as "XYZ " appearing as XYZ but actually needing "XYZ " to work > >(note the trailing blank). I would like to side with the "bug" group, but I can't remember the answer we got on this one when we received our first "baby" router about a year ago. In our case, we created the config file on an IBM mainframe with fixed-length records (padded with spaces). The problem was discovered when we created the config file on a Sun and it worked. > > A minor related complaint is that the "enable-password" command doesn't need > to be entered as a complete name. "enable" is sufficient. I got caught > by this when enabling CLNS via the terminal configuration and transposed > "clns enable" to "enable clns". It took a while to figure out what I did. > It makes for great fun trying to figure out what happened when you can't > become enabled and the new password was written to NVRAM. In our case, one of our remote sites was trying to reconfigure the device connected to the console port and inadvertently caused "enable xxxx" (where xxxx was some command for the terminal which I forget). Fortunaetly, the person who did this managed to recall what he did after some probing questions. > > I think the enable-password should be required to be typed in completely > to avoid catching people by surprise. I agree! > > Doug McCallum > Interactive Systems Corp. > dougm@ico.isc.com Pierre Fortin fortinp@bnr.ca Yeah I know; still no signature...