You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only problem I ran into when trying to use this module was when the client sends it's data to the server side there is no way to view what that data was sent with out doing a bunch of useless work, in the case I was trying to use the module, I was trying to write a simple telnet honeypot that just logged what data the user sent to the server along with the ip address and port. The only way to get this working was to modify def handle and add a few lines off code to log it (which broke the unknown command writerror and I haven't took the time to figure out why since what I need the code to do is working), this raised a bunch of flags in my head of why there wasn't an easier way to get this info without having to modify the handler, why would anyone run a server without logging what the people who access the server has done or at least be able to enable a way to view the data sent to the server, is there an easier way and am I missing it, only thing I didn't try was changing the stdout but that just would raised further problems away from my intended use, and for what should have been a simple 25-30 lines of code turned into 55-60. All I wish for this module is there was an already included option to view and log what the client has sent with out having to modify the module or code itself, I would do it but my intended use with this module is done and will have no further need for unless I need to create another telnet honeypot, like I said I don't know who in this day and age would want to run a service on a server that didn't have a way to view what the client's input is to the server
The text was updated successfully, but these errors were encountered:
The only problem I ran into when trying to use this module was when the client sends it's data to the server side there is no way to view what that data was sent with out doing a bunch of useless work, in the case I was trying to use the module, I was trying to write a simple telnet honeypot that just logged what data the user sent to the server along with the ip address and port. The only way to get this working was to modify def handle and add a few lines off code to log it (which broke the unknown command writerror and I haven't took the time to figure out why since what I need the code to do is working), this raised a bunch of flags in my head of why there wasn't an easier way to get this info without having to modify the handler, why would anyone run a server without logging what the people who access the server has done or at least be able to enable a way to view the data sent to the server, is there an easier way and am I missing it, only thing I didn't try was changing the stdout but that just would raised further problems away from my intended use, and for what should have been a simple 25-30 lines of code turned into 55-60. All I wish for this module is there was an already included option to view and log what the client has sent with out having to modify the module or code itself, I would do it but my intended use with this module is done and will have no further need for unless I need to create another telnet honeypot, like I said I don't know who in this day and age would want to run a service on a server that didn't have a way to view what the client's input is to the server
The text was updated successfully, but these errors were encountered: