-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple errors when using rdpy-rdphoneypot.py #100
Comments
I am also getting the error reported as item 5:
I understand that some malformed traffic will be sent as a byproduct of port scanning/etc. but wanted to echo that this is in multiple environments. If anticipated, can we have a |
Downgrade Twisted to 19.2.1, I was seeing these errors only in newer versions. Seems they changed something in newer versions and @citronneur does not appear to be active so upgrading probably won't be happening. |
OK i will check soon. I'm working on the python 3 version. |
Oh, man, nice to hear back from you! I've started making an RDP honeypot of my own, based on this library. I'd like it to be able to run in Python3 too, so I and another guy have started porting the library. Man what a pain in the butt... We're nowhere near ready yet, but if you would like to take a look (maybe it would save you some time?), give me some e-mail address (could be a throw-away one) to which to send the invite. The repo is on GitLab and it isn't public yet. |
Hi, I also get the same error when scanning RDPY honeypot with nmap script. The nmap command: The error message :
I've tried to downgrade twisted to 19.2.1 , which @hackdefendr advised before. But it didn't works either. |
@citronneur are there any news regarding a "new" python 3 version?
|
Hello, I am having same issue. Any news on a fix or python 3 port? |
I tried setting up an RDP honeypot using
rdpy-rdphoneypot.py
but it was an utter failure becauserdpy-rdphoneypot.py
is broken in multiple ways, essentially making it unusable.When connecting to the honeypot manually with a Windows 7 RDP client, it sort of works, in the sense that I am shown the recorded session. However, I am never asked for a password and no password is recorded in the log. Somebody has asked how to fix this problem in issue How does rdpy-rdphoneypot make a client prompt for a username or password #93 but never got a reply.
When actual attackers connect to the honeypot, it seems that the RDP protocol is not quite compatible with theirs. As a result, the honeypot logs only the connection but no username, password, etc.:
Issue #25 suggests that this happens when the attacking tool Hydra is used because of some kind of protocol incompatibility. Any chance of this problem being solved?
Somebody has asked what it means in issue #66 but never got a reply.
I have no idea what that means but it's probably again some kind of protocol incompatibility with some attacking tool.
Is there any chance of these problems ever getting fixed or should I give up on the idea of using this tool as an RDP honeypot?
The text was updated successfully, but these errors were encountered: