Describe the bug
RSA keys seems to be supported and it is technically possible to login with RSA pub keys. But there is no documentation about how can you configure to allow login with any RSA key

To Reproduce
Steps to reproduce the behavior:

1. ssh root@server -i mykey.rsa
2. Access denied

2019-08-19T14:49:13.425705Z [cowrie.ssh.factory.CowrieSSHFactory] New connection: 10.0.

• T-Pot 19.03 Standard Installation on Debian sid
• Hardware (i5-540M)

I'm trying to activate SSL for Elasticsearch because I want to connect to it with remote Logstash instances.

• I generated a certificate with the elasticsearch-certutil following this guide: https://www.elastic.co/guide/en/elasticsearch/reference/7.3/configuring-tls.html
• I placed the certificate in /data/elk/
• I als

Hello...
I've been trying to use this command to scan Conpot and get information from it:
nmap -A -Pn -p1-1000 172.20.10.2

The output of this scan will come back as in the photo shown bellow:

The Conpot's output console will stop in

datanode:
port: 50075

GET /jmx?qry=Hadoop:service=DataNode,name=DataNodeInfo HTTP/1.1
GET /jmx?qry=Hadoop:service=NameNode,name=FSNamesystemState HTTP/1.1

namenode:
port: 50070

GET /jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo HTTP/1.1

ISSUE TYPE

• Bug Report
• Feature Idea
• Documentation Report

DIONAEA VERSION

0.8.0
baf25d6d40db7018562e22c03b60b4f43317f206

I would like to improve the developer documentation and got something like this in mind:

• provide a boilerplate for a new plugin
• provide a boilerplate for a new logger
• explain development of both step by step (like how its done in the Plugins section already)

What do you think? Is there something else to include?

There is plenty of opportunity to add more tests to SNARE. We make a lot of assumptions and with GSoC approaching, we should make sure the critical paths are covered.