Skip to content

GRR release 3.4.9.0

Latest
Compare
Choose a tag to compare
@mbushkov mbushkov released this 27 Feb 13:05
· 1 commit to master since this release
44adfce

This is a regular GRR release.

IMPORTANT: It's the last release containing the legacg UI and the legacy API support (UIv1 and APIv1). In the next release:

  • The APIv1 will be removed. If you use the GRR API Python client library, you shouldn't notice anything. If you use direct HTTP JSON requests to talk to GRR AdminUI, you need to ensure that you're using APIv2 (contains /v2/ in the URLs).
  • The UIv1 (legacy AngularJS-based UI) will be removed and the much improved version of the Angular-based UIv2 will become the only UI available. Between the current and the next release UIv2 will get additional debugging capabilities, a denser UI layout, the implementation of missing flows, performance improvements etc.

Changelog for the current release:

Added

  • Added support for listing %SystemDrive%\Users as a supplementary mechanism
    for collecting user profiles on Windows (additionally to using data from the
    registry).

Removed

  • Removed the ListFlowApplicableParsers API method.
  • Removed the ListParsedFlowResults API method.
  • Removed support for the GREP artifact source (these were internal to GRR and
    not part of the official specification.
  • Removed ApiClient.users field which contained duplicate information present in ApiClient.knowledge_base.users field.
  • Removed no longer used or relevant configuration options:
    • Server.fleetspeak_enabled
    • Client.fleetspeak_enabled
    • Client.server_urls
    • Client.control_urls
    • Client.server_serial_number
    • Client.poll_min
    • Client.poll_max
    • Client.error_poll_min
    • Client.labels
    • Client.rss_max
    • Client.rss_max_hard
    • Frontend.bind_port
    • Frontend.port_max
    • Nanny.child_binary
    • Nanny.child_command_line
    • Nanny.service_name
    • Nanny.service_description
    • Nanny.statusfile
    • Nanny.binary
    • Nanny.service_binary_name

Changed

  • Renamed restricted_flow_users and restricted_flow_groups to admin_users
    and admin_groups. The new entries can be used to grant access for
    Client/Hunt/CronJob approvals as well as restricted flows.