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
51
52
|
Source: wforce
Maintainer: Neil Cook <neil.cook@open-xchange.com>
Section: web
Priority: optional
Standards-Version: 3.9.2
Build-Depends: cdbs,
autoconf,
automake,
debhelper (>= 9.20160709),
dh-autoreconf,
libboost-all-dev (>= 1.4.0),
libcurl4-openssl-dev,
wforce-lua-dist,
libgetdns-dev,
libhiredis-dev,
libmaxminddb-dev,
libprotobuf-dev,
libreadline-dev,
libssl-dev,
libsodium-dev,
libsystemd-dev,
libyaml-cpp-dev,
libjsoncpp-dev,
uuid-dev,
libz-dev,
libtool,
pkg-config,
protobuf-compiler,
asciidoctor,
wget
Package: wforce
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Daemon for detecting brute force attacks
The goal of 'wforce' is to detect brute forcing of passwords across many
servers, services and instances. In order to support the real world, brute
force detection policy can be tailored to deal with "bulk, but legitimate"
users of your service, as well as botnet-wide slowscans of passwords.
The aim is to support the largest of installations, providing services to
hundreds of millions of users.
Package: wforce-trackalert
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Longterm abuse data reporting and alerter
Trackalert is designed to be an optional service to complement
wforce. Whereas wforce provides a toolkit to combat abuse of
logins such as password brute forcing in realtime, trackalert is
designed to look at abuse asynchronously, using long-term report data
stored in an external DB such as elasticsearch, and to send alerts on
potential login abuse.
|
