From ab1355edf492be0ed4fb1be07e91243a9a4fb511 Mon Sep 17 00:00:00 2001 From: Mehtab Zafar Date: Sun, 17 Mar 2019 12:42:28 +0530 Subject: [PATCH] Add FAQs (#1053) --- docs/FAQ.rst | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 docs/FAQ.rst diff --git a/docs/FAQ.rst b/docs/FAQ.rst new file mode 100644 index 00000000..a0717dbf --- /dev/null +++ b/docs/FAQ.rst @@ -0,0 +1,29 @@ +Frequently asked questions +###### + +Why can't I start cowrie on port 22? +*********************************** + +The possible answer for that is you might already have a service(possibly SSH) running on that port so setting up Cowrie on that port will cause a problem. Try changing the port in `listen_endpoints` present in config file(cowrie.cfg.dist/cowrie.cfg). + +Why do I get logged into my own system when accessing cowrie on port 22? +********************************************************************* + +This is probably a similar problem as it was in the above question. This can also be fixed by changing the port in the config file. + +What I am getting permission denied when running cowrie on port 22? +***************************************************************** + +You need root privileges to run Cowrie on any port lower than 1024. This can be fixed by setting up `Authbind `_. + +Do I need to copy all the content of cowrie.cfg.dist to cowrie.cfg? +******************************************************************* + +No, Cowrie can read add your only local changes to cowrie.cfg and the remaining settings will automatically be read from cowrie.cfg.dist + + +Why certain commands aren't implemented? +*************************************** + +There are lots of UNIX command implemented in cowrie and that is because Cowrie is more focused to provide proxy support i.e use Cowrie to connect to an actual machine that is actual machine having support for all the UNIX functionalities. +