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.

Hello everyone!
I have a few doubts on how events are handled across misp instances and Orgs. As I still haven't complete domain of the code and my curiosity is killing me, I'm coming here to ask help =]

1. In the situation a site admin edit an event from another org and publish it. What exactly will happen with that information? Supposing it has a distribution level as "All communities".
   Wil

Description

Package uwsgi from Ubuntu repo is advised in production usage, but it is too old and won't work. File yeti_uwsgi.service has -w switch which is absent in this package.

Pip version works, probably it's sufficient to add uwsgi to requirements.txt

Environment

Create an interface within the plugin to add notes, tags and other manually captured items analysts might want to keep track of, and have the notes displayed in the popups as well.

Any feedback or ideas for this are welcome.

IMHO it's good to remove examples which use deprecated methods.
Those examples are obstacles to learn how to use PyMISP in the latest manner.

Although there are a number of documentation pages on the OpenTAXII web site (i.e. http://www.opentaxii.org/en/stable/configuration.html), there does not appear to be anything that provides a comprehensive detailed reference for the configuration parameters that can be used.

Does this information exist somewhere?

Add the ability for using certificate-based authentication for the taxii-proxy command.

At the moment text in the STIX Indicator:Description field is lost. It would be nice to convert this to an attribute comment in MISP.

The same is true for the stix:Description field which could be converted to Catergory=other Type=comment in MISP.

The MISP instance is currently built without configuring GnuPG or generating a key. We should document how to set this up and.or automate the process.

The current RFC for misp-core-format has two different timstamp formatings:

1. unix timestamp format as string value (REF: #3)
2. date as YYYY-MM-DD

To conform with standard API marshaling and unmarshaling the timestamps should all be formated conform with RFC 3339 (https://tools.ietf.org/html/rfc3339)

Documentation is now hosted on the cloud node. It would be nice to provide a simple administrator interface on top of the cloud node to manage users and see the latest data.