Closed
Milestone
started on Jan 31, 2022
2.9
Additional improvements in Mentat 2.x series
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
23
- Update reporter templates to support different wording for severity
- PassiveDNS REST API token displayed to user on connection error
- Upgrade PostgreSQL to v14
- mentat-enricher.py error in Vagrant box
- mentat-controller.py not working with jinja2 version 3.0.1.
- Cancel buttons are validating fields
- menat-controller.py --command disable shows error
- IPv6 addresses are not shown in report details
- Viewing details of abuse group in reports/dashboard results in internal server error
- Cancelling creation of network record results in internal server error
- When daemons run in parallel, pid files are generated with wrong PID in name
- Warnings by pyflakes on build
- Buildbot warnings on mentat-deb
- Store email addresses to which the report was sent
- Erroneous values in mentat_main/reports_events/mail_to
- Wrong usage of DB array in mentat_main/settings_reporting/emails
- Notification mails about new users for the group do not seem to go to group admin
- Link report to each group which owns it
- Use Vagrant as alternative tool for local development
- Move attachments from emails to web
- Simplify/remove too detailed user settings for reporting
- Incorporate new info from Negistry into group db and reporting
- Review encapsulation of SQLAlchemy and Psycopg2 DBALs
Loading
Loading
Loading