Exception caught
Closed this issue · 5 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
Not sure, during the lat 10 -11 days ive only seen this happen twice.
What is the expected output?
Normal log entries(?)
What do you see instead?
2014-03-12 05:26:37+0100 [HonsshServerTransport,1376,pesky.ip.add.ress]
Unhandled Error
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/twisted/python/log.py", line 84, in callWithLogger
return callWithContext({"system": lp}, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/log.py", line 69, in callWithContext
return context.call({ILogContext: newCtx}, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/local/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/local/lib/python2.7/site-packages/twisted/internet/posixbase.py", line 581, in _doReadOrWrite
why = selectable.doRead()
File "/usr/local/lib/python2.7/site-packages/twisted/internet/tcp.py", line 199, in doRead
rval = self.protocol.dataReceived(data)
File "/usr/local/lib/python2.7/site-packages/twisted/conch/ssh/transport.py", line 438, in dataReceived
self.dispatchMessage(messageNum, packet[1:])
File "/HONEY/honssh/server.py", line 201, in dispatchMessage
self.client.sendPacket(messageNum, payload)
exceptions.AttributeError: HonsshServerTransport instance has no attribute 'client'
2014-03-12 05:26:37+0100 [HonsshServerTransport,1376,pesky.ip.add.ress]
connection lost
What version of the product are you using?
b9880b4e367b
On what operating system?
OpenBSD 5.4
Please provide any additional information below.
Totally forgot to enable advanced logging, doing that now and including it if
it happens again :)
Original issue reported on code.google.com by are.hans...@gmail.com
on 12 Mar 2014 at 6:48
GoogleCodeExporter commented
Thanks man. This confuses me so any advanced logging will be helpful - I'll
look into it more over the weekend :)
Original comment by tnn...@googlemail.com
on 12 Mar 2014 at 6:59
- Changed state: Accepted
GoogleCodeExporter commented
Yepp, enbaled the advanced logging now.
Ive only seen it twice in +4000 attacks so it might take a while :)
Original comment by are.hans...@gmail.com
on 12 Mar 2014 at 7:15
GoogleCodeExporter commented
I just had this exact same error just as I started coding. I realised it was
because I had the wrong IP addresses in the cfg file. I'm guessing this isn't
the case for you but maybe there was something else preventing HonSSH from
reaching the honeypot?
Original comment by tnn...@googlemail.com
on 16 Mar 2014 at 2:33
GoogleCodeExporter commented
I dont think tht is the case here. The two instances i've seen this has been
after HonSSH has been running for a while.
Ill be running HonSSH for another week or so before i take it off line for
maintenance and upgrades, but ill let you know if i see this issue again.
Original comment by are.hans...@gmail.com
on 16 Mar 2014 at 4:01
GoogleCodeExporter commented
Create a new issue if this does come up again - most likely a bug somewhere :P
Original comment by tnn...@googlemail.com
on 16 Mar 2014 at 5:58
- Changed state: Done