Skip to content

Athena

Compare
Choose a tag to compare
@vkotronis vkotronis released this 10 Apr 14:17
· 785 commits to master since this release

This release includes the following changes:

Added

  • Support for dormant flags in hijacks
  • Storing hijack update (origin, neighbor) combinations in redis
  • Learn rule action for ongoing hijacks in frontend after ignore action
  • Misc UI additions
  • Initial kubernetes/helm (helm-charts) support
  • Reject old updates from taps and have a "HISTORIC" variable to enable/disable
  • Initial support for LDAP authentication
  • Hijack deletion functionality
  • Abuse contact details for each ASN (Extracted from RIPEStat)
  • Functionality to copy ASN details on clickboard
  • Support to filter BGP Updates based on their AS Path
  • Display distinct values of BGP Updates for the following fields: "Origin AS", "Peer AS" and "service" in hijack view

Changed

  • Using prefix lists in json file format as monitoring taps input to avoid problematic ultra long arguments
  • Refactored environment variables
  • Use of RIPE RIS firehose stream instead of the websocket clientui8
  • Misc UI improvements
  • Update hasura (1.0.0alpha31 -> 1.0.0alpha42)
  • Hijack view now uses hasura graphql to fetch BGP Updates

Fixed

  • Correct RFC2622 translation when needed in frontend and backend
  • When learning ignore rule, escape special character ":" (IPv6)
  • Problematic start of RIS and exaBGP monitors, even if not configured
  • BGP update redis bootstraping from DB
  • UI support for multiple instances of a module in overview and system page
  • Misc UI bugs

Removed

  • Configured prefix graph visualization (needs redesign)
  • Config data field from configs DB table

Security

  • Using yaml dump and safe_load instead of pickling/unpickling

You can view a more detailed list of changes in the CHANGELOG (https://github.com/FORTH-ICS-INSPIRE/artemis/blob/master/CHANGELOG.md). You can follow the wiki guide here (https://github.com/FORTH-ICS-INSPIRE/artemis/wiki#upgrading-artemis-to-a-new-version) to upgrade to the new version. Note: this release requires a DB migration, which is automatically handled by the system.