Skip to content

LUNA PLATFORM v.5.53.0#

Summary#

  • The VisionLabs image for PostgreSQL has been updated from version 12 to version 16.

    If you previously used this image, then to migrate to the new version you must perform the migration yourself according to official documentation. If necessary, you can continue to use PostgreSQL 12 by specifying the "postgis-vlmatch:12" image in the container launch command.

    Mounting PostgreSQL 12 data from the "/var/lib/luna/postgres" directory into a PostgreSQL 16 container will result in an error.

    The section "Migrate PostgreSQL 12 to PostgreSQL 16" has been added to the upgrade manual, containing a reminder about the need for migration.

  • The ability to detect facial spoofing using DeepFake technology in photo images has been added.

    The "estimate_deepfake" parameter has been added to the requests "create handler", "create verifier" and "sdk".

    The "deepfake" field has been added to the event structure. This field can be used as a value for the "target" field or as a filter to receive an event using GET requests.

    Deepfake estimation may return the following results:

    • "prediction" = "fake" - The person is not real.
    • "prediction" = "real" - The person is real.
    • "score" = [0...1] - The degree of reliability of the estimation.

    In requests "create handler" and "create verifier" it is possible to set the "real_threshold" and "mode". The "sdk" request will use the default values of these parameters without the possibility of explicitly specifying them.

    Using the "real_threshold", you can set a value in the range [0...1], below which the system will consider that the person is not real.

    Two operating modes are available:

    • "mode" = "1" - Simplified operating mode.
    • "mode" = "2" (default) - Operating mode using an additional neural network model for preliminary estimation. If the result of the preliminary estimation determines that the person is fake, then the result "score" = "0" and "prediction" = "fake" will be returned in the response body.

    The following image requirements must also be met to perform the estimation:

    • head pose: "pitch" = [-20...20]
    • head pose: "yaw" = [-30...30]
    • face width: "face_width" > 150

    The "deepfake" filter can also be used in matching requests.

    The "deepfake_states" parameter has also been added to the handler and verifier, which allows filtering events by the expected result of the Deepfake estimation.

    The "deepfake" field has also been added to the filters for Clustering, Exporter, Cross-matching and Linker tasks. For the Exporter and Reporter tasks, the field is supported as a column.

    The "deepfake" field has also been supported as a filter in the "ws handshake" request.

  • A new request "get list of plugins" has been added to the API service, which enables you to get a list of imported plugins and their status.

  • A new "callbacks" policy has been added to the "storage_policy" of the handler and verifier, with which you can send generated events (notifications) to the third-party system at the specified URL.

    In fact, callbacks are analogous to sending notifications via web sockets, but with the key difference that they use the principles of HTTP webhooks, which provides a more flexible and customizable mechanism for sending notifications to third-party systems. You can configure the protocol type, external system address, request parameters and authorization data.

    Events sent using the "callbacks" field have a format corresponding to the format of the "generate events" request.

    For more information, see the requests "create handler" and "create verifier".

  • The Handlers-lambda input data structure has been updated.

    This means that all existing lambdas must be revised and recreated according to the new structure.

    All examples have also been updated.

    Example of the old input data structure: {"body": getImage("empty.jpeg"), "filename": "empty.jpeg", "source_type": 0}

    Example of a new input data structure: {"source": {"body": getImage("empty.jpeg")}, "filename": "empty.jpeg", "source_type": "raw_image"}

  • Now the Kaniko executor image (the image for building lambda) should be in the registry specified in the "LAMBDA_REGISTRY" setting.

    Instructions for transferring the Kaniko executor image from the VisionLabs registry to the user registry have been added to the installation manual.

  • New connection settings with Redis and Redis Sentinel have been added.

    The "user" parameter has been added to the settings groups "REDIS_DB_ADDRESS", "TASKS_REDIS_DB_ADDRESS", "LUNA_ATTRIBUTES_DB", "BACKPORT3_EVENTS_DB_ADDRESS".

    The "user" and "password" parameters have been added to the "sentinel" section of the above settings.

  • Guardant has been updated from version 3.15 to 3.22.

API (v.6.19.7 - v.6.20.1)#

Improvements#

Faces (v.4.8.31 - v.4.9.0)#

Improvements#

  • Support for Redis username auth option. For LUNA_ATTRIBUTES_DB configuration, user parameter added.

  • Support for Redis Sentinel auth configuration. For LUNA_ATTRIBUTES_DB.SENTINEL config section, user & password parameters added.

  • Service dependencies were updated.

Image Store (v.3.9.26 - v.3.9.28)#

Improvements#

  • Service dependencies were updated.

Accounts (v.0.1.31 - v.0.1.33)#

Improvements#

  • Service dependencies were updated.

Tasks (v.3.17.11 - v.3.18.0)#

Improvements#

  • Support for Redis username auth option. For TASKS_REDIS_DB_ADDRESS configuration, user parameter added.

  • Support for Redis Sentinel auth configuration. For TASKS_REDIS_DB_ADDRESS.SENTINEL config section, user & password parameters added.

  • The deepfake event field was supported as filter for several tasks:

  • clustering task .
  • exporter task .
  • cross matching task .

  • linker task .

  • The deepfake event field was supported as target column for exporter/reporter tasks. See exporter task . See reporter task .

  • Service dependencies were updated.

Events (v.4.9.11 - v.4.10.1)#

Improvements#

  • Service dependencies were updated.

  • Field deepfake was added to event. Can be used as filter for get_events and event specification.

Configurator (v.2.1.66 - v.2.1.70)#

Improvements#

  • Service dependencies were updated.

Sender (v.2.7.11 - v.2.9.0)#

Improvements#

  • Support for Redis username auth option. For REDIS_DB_ADDRESS configuration, user parameter added.

  • Support for Redis Sentinel auth configuration. For REDIS_DB_ADDRESS.SENTINEL config section, user & password parameters added.

  • The deepfake event field was supported as filter for ws handshake .

  • Service dependencies were updated.

Admin (v.5.4.8 - v.5.4.10)#

Improvements#

  • Service dependencies were updated.

Fixed bugs#

  • The Internal server error was fixed for requests get sys info request. The error was occurring when the influxdb database did not have the required measurements.

Licenses (v.0.8.10 - v.0.8.14)#

Improvements#

  • Service dependencies were updated.

  • HASP library updated to version 1.8.2.

Handlers (v.3.1.10 - v.3.2.0)#

Improvements#

  • Support for Redis username auth option. For REDIS_DB_ADDRESS configuration, user parameter added.

  • Support for Redis Sentinel auth configuration. For REDIS_DB_ADDRESS.SENTINEL config section, user & password parameters added.

  • Handler & verifier detection policy was extended with deepfake estimation policy & deepfake state filter.

    See the estimate_deepfake and deepfake_states parameters in handler detect policy , verifier detect policy .

  • Handler storage & matching & additional tags policies were extended with deepfake state filter.

    See the deepfake option in filters in handler storage / match / conditional_tags policies .

  • Generated event structure extended with deepfake estimation & filtration results.

    See save raw event , generate event .

  • Field callbacks was added to notification policies.

    Each callback allows to send generated events to the third party system by specified url.

    Events sent using callback have corresponding format with ones from generate event resource.

    See generate events , create handler , validate handler policies .

  • The generate stream events (beta) was updated.

Python Matcher and Python Matcher Proxy (v.1.6.22 - v.1.6.23)#

Improvements#

  • Support for events` deepfake field was added. The "deepfake" field can be specified as a target and as a filter for the candidates of the "event" type.

  • Service dependencies were updated.

Backport3 (v.0.8.28 - v.0.8.29)#

Improvements#

  • Service dependencies were updated.

Backport4 (v.1.3.31 - v.1.3.32)#

Improvements#

  • Service dependencies were updated.

Remote Sdk (v.0.2.7 - v.0.2.8)#

Improvements#

  • Service dependencies were updated.

Lambda (v.0.0.7 - v.0.0.8)#

Improvements#

  • Service dependencies were updated.

  • The handlers lambda incoming data structure was updated. It means that all existing lambdas must be revised and recreated in accordance with the new structure. All examples have also been updated.

  • The kaniko image (image for lambda building) from now on is expected registry specified as LAMBDA_REGISTRY in service configuration.