Skip to content

Conversation

@regulartim
Copy link
Collaborator

@regulartim regulartim commented Nov 27, 2025

Description

This PR introduces a new API endpoint: the CowrieSession API. It is meant to be (1) a replacement for the already existing CommandSequence API but also comes with new functionality. Compared to the CommandSequence API, the following things are changed:

  • responses have the same structure, regardless if a IP address or a command sequence was queried
  • responses optionally include the credentials used across matching Cowrie sessions
  • responses optionally include detailed information about matching Cowrie sessions

Related issues

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

  • I have read and understood the rules about how to Contribute to this project.
  • The pull request is for the branch develop.
  • I have added documentation of the new features.
  • Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved. All the tests (new and old ones) gave 0 errors.
  • If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.

@regulartim regulartim marked this pull request as ready for review December 1, 2025 07:39
@regulartim regulartim requested a review from mlodic December 1, 2025 07:39
@regulartim regulartim merged commit 4e42262 into develop Dec 1, 2025
5 checks passed
@regulartim regulartim deleted the session_api branch December 1, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants