Open int3rlop3r opened 5 years ago
Is there any release scheduled this week?
I suppose that the same problem will appear for any telnet server, which can use binary telnet transmittion (RFC 856), because the TRANSMIT-BINARY equal 0 (zero).
We see this when we use exscript to connect to telnetlib3.server, for example (python3 -m telnetlib3.server
). In this case can see the traceback:
Traceback (most recent call last): File "/.../Exscript/workqueue/job.py", line 78, in run self.function(self) File "/.../Exscript/queue.py", line 102, in _wrapped result = func(job, host, conn, *args, **kwargs) File "/home/yren/workspace/sandbox/python-test/telnet/simple-exscript.py", line 8, in do_something conn.expect('tel:sh') File "/.../Exscript/protocols/protocol.py", line 1058, in expect result = self._expect(prompt) File "/.../Exscript/protocols/protocol.py", line 1033, in _expect result = self._domatch(to_regexs(prompt), True) File "/.../Exscript/protocols/telnet.py", line 85, in _domatch result, match, self.response = func( File "/.../Exscript/protocols/telnetlib.py", line 754, in expect return self._waitfor(relist, timeout, True, cleanup=cleanup) File "/.../Exscript/protocols/telnetlib.py", line 672, in _waitfor self.process_rawq() File "/.../Exscript/protocols/telnetlib.py", line 545, in process_rawq command == WILL and 'WILL' or 'WONT', ord(opt)) TypeError: ord() expected a character, but string of length 0 found
There are some versions of Nexus switches that have a null byte in their prompt - '\x00' and hence doesn't match the prompt re even though the driver was set to
nxos
.