File: control

package info (click to toggle)
fever 1.0.16-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 768 kB
  • sloc: sh: 33; makefile: 18
file content (50 lines) | stat: -rw-r--r-- 1,907 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Source: fever
Section: net
Priority: optional
Maintainer: Sascha Steinbiss <satta@debian.org>
Build-Depends: debhelper-compat (= 13),
 dh-golang,
 golang-go (>= 2:1.12),
 golang-github-buger-jsonparser-dev,
 golang-gopkg-pg.v5-dev,
 golang-github-voxelbrain-goptions-dev,
 golang-github-streadway-amqp-dev,
 golang-github-sirupsen-logrus-dev,
 golang-github-gorilla-mux-dev,
 golang-gopkg-mgo.v2-dev,
 golang-github-dcso-bloom-dev (>= 0.2.2),
 golang-github-dcso-fluxline-dev,
 golang-github-spf13-cobra-dev,
 golang-github-spf13-viper-dev,
 golang-github-garyburd-redigo-dev,
 golang-github-stvp-tempredis-dev,
 golang-github-neowaylabs-wabbit-dev,
 golang-github-yl2chen-cidranger-dev,
 golang-github-patrickmn-go-cache-dev,
 golang-goprotobuf-dev (>= 1.3),
 golang-google-grpc-dev (>= 1.22)
Standards-Version: 4.5.0
Rules-Requires-Root: no
XS-Go-Import-Path: github.com/DCSO/fever
Vcs-Browser: https://salsa.debian.org/debian/fever
Vcs-Git: https://salsa.debian.org/debian/fever.git
Homepage: https://github.com/DCSO/fever

Package: fever
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
Recommends: suricata
Built-Using: ${misc:Built-Using}
Description: fast, extensible, versatile event router for Suricata's EVE-JSON format
 The Fast, Extensible, Versatile Event Router (FEVER) is a tool for fast
 processing of events from Suricata's JSON EVE output. What is meant by
 'processing' is defined by a number of modular components, for example
 facilitating fast ingestion into a database. Other processors implement
 collection, aggregation and forwarding of various metadata (e.g.
 aggregated and raw flows, passive DNS data, etc.) as well as performance
 metrics.
 .
 It is meant to be used in front of (or as a replacement for) general-purpose
 log processors like Logstash to increase event throughput as observed on
 sensors that see a lot of traffic.