Publicly viewable attack map

[TheTrueColonel]

Is your feature request related to a problem? Please describe.
Not entirely. I'd just like to show off my attack map without requiring credentials.

Describe the solution you'd like
I'd like to see a maybe a separate port/route for an attack map for public display. Maybe with a more limited view. (e.g. Hidden IP addresses)

[t3chn0m4g3]

@TheTrueColonel - We just moved the feature request to the T-Pot Attack Map repository which is better suited since we do not plan to adjust T-Pot to openly expose the attack map. Especially with regard to the data being offered this would be counterproductive. Also adjustment of the code to reduce the exposed data will require adjustments of the complete pipeline (ES queries, CSS / JS, publishing logic, etc.) to avoid exposing the data on the client side through websocket messages.

If you still want to openly grant access to the attack map it is suggested to make use of the tiered architecture of the attack map (DataServer, AttackMapServer, Redis). Run the DataServer on the Hive to directly access ES via http://127.0.0.1:64298 and publish to a separate Redis instance (adjust these lines accordingly).

Run the AttackMapServer behind a reverse proxy on a separate machine by adjusting these lines accordingly.

We will keep the feature request open for some time, however, as mentioned above, we are not planning to integrate that feature.

Thanks for understanding.