Is it not possible that, instead of somebody pasting wierd characters into
a telnet client, it could actually be a pointer bug? I've had this problem
after I'd fiddled with some of the comm.c, interpreter.c & db.c code, and
I eventually tracked it down to a pointer left with a random value.
Of course, it could well be someone pasting into the client, but pointer
problems are a very common cause of strings appearing like this, as most C
programmers will know.
> One I have noticed from all this is that when a person logs in with the
> password like çñÿ¿Dëÿ¿. That's the bug and by not accepting letters not
> on the keyboard as a name will fix this. I'm not sure if you need to
> change this in the password though.
Mo.
--
Mo McKinlay
Development and Support Manager
IDSS Department
Bekon
2 North Place
Stockport
Cheshire
SK1 1HH
T: +44 (0) 161 476 1300 x224
F: +44 (0) 161 476 1311
E: M.McKinlay@bekon.com
W: http://www.bekon.com/idss/
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST