Ok..... But that needs to be configured. As in: It is not the default.
I tried - maybe once - to set up use names, but failed, so didn't continue on that line as there was no need at that point.
Going off topic here so #i won't carry on much more after this unless others are also interested, but...
Setting a password and enabling telnet only requires a few lines of config (set a vty password, set an enable password, enable telnet).
Personally something like that I'll add the config but not save over serial. Then login over telnet /ssh, once logged in over telnet/ssh save the config. That way if it doesn't work you still have an active serial login you can use to revert the config. And in a worst case scenario you can reboot to restore the last saved config.
When looking at longer things (like the output of sh log, or enabling debug modes) a telnet session is much faster. looking at 1000's of log lines over 9600bd serial is slow and annoying.
There's an extension of the reboot to get a old config back that's good when configuring a remote site.
2) Save config
3) set a reboot (reload in 20, or reload at 08:30)
4) make changes
5) reload cancel
6) save config (possible after a period to check for issues)
The benefit being that if your changes do cut you off, the programmed reboot will restore the previous config. If it all works you can cancel the reboot before the scheduled time (every time I've used that process the config has gone well, the few times I've not done it there's been a frantic phoning around to find someone on the remote site or a drive up the motorway to fix it).