You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Added `--update-database` option (PR#1524 by Filip Pokorný).
98
98
- Added `api_token` parameter (PR#1524 by Filip Pokorný).
99
99
- The script `update-rfiprisk-data` is now deprecated and will be removed in version 3.0.
@@ -144,7 +144,7 @@ IntelMQ no longer supports Python 3.5 (and thus Debian 9 and Ubuntu 16.04), the
144
144
- Ignore non-zero exit-codes for the `intelmqctl check` call in postinst (#1748, by Sebastian Wagner).
145
145
146
146
### Tests
147
-
- Added tests for `intelmq.lib.exceptions.PipelineError`.
147
+
- Added tests for `intelmq.lib.exceptions.PipelineError` (by Sebastian Wagner).
148
148
-`intelmq.tests.bots.collectors.http_collector.test_collector`: Use `requests_mock` to mock all requests and do not require a local webserver (by Sebastian Wagner).
Copy file name to clipboardExpand all lines: NEWS.md
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,23 @@
1
1
NEWS
2
2
====
3
3
4
-
See the changelog for a full list of changes.
4
+
This file lists all changes which have an affect on the administration of IntelMQ and contains steps that you need to be aware off for the upgrade.
5
+
Please refer to the changelog for a full list of changes.
5
6
6
7
2.3.0 Bugfix release (unreleased)
7
8
----------------------------------
8
9
9
-
The documentation is now available at [intelmq.readthedocs.io](https://intelmq.readthedocs.io/) (FIXME: Link to stable version?).
10
+
The documentation is now available at [intelmq.readthedocs.io](https://intelmq.readthedocs.io/).
10
11
11
12
### Requirements
12
13
IntelMQ no longer supports Python 3.5 (and thus Debian 9 and Ubuntu 16.04), the minimum supported Python version is 3.6.
13
-
CentOS 7 (with EPEL) provides both Python 3.4 and Python 3.6. If IntelMQ was installed with Python 3.4, the code needs to be re-installed with Python 3.6 and removed for Python 3.4. Application data is compatible. To install the Python 3.6 packages, use: `yum install python36 python36-devel python36-requests`.
14
-
15
-
### Tools
14
+
CentOS 7 (with EPEL) provides both Python 3.4 and Python 3.6. If IntelMQ was installed manually with Python 3.4, the code needs to be re-installed with Python 3.6 and removed for Python 3.4. Application data is compatible. To install the Python 3.6 packages, use: `yum install python36 python36-devel python36-requests`.
16
15
17
16
### Bots
18
17
19
18
#### Bot option `--update-database`
20
19
- Bots that require a database file (such as `maxmind_geoip`, `asn_lookup`, `tor_nodes` and `recordedfuture_iprisk`)
21
-
have new command line option `--update-database`. It is not necessary to specify a
20
+
have a new command line option `--update-database`. It is not necessary to specify a
22
21
bot ID, the function automatically updates the database for all the bots of the same
23
22
type and reloads them afterwards. Removes any external dependencies (such as curl or wget).
24
23
This is a replacement for shell scripts such as `update-tor-nodes`, `update-asn-data`,
@@ -41,7 +40,7 @@ If you depend on this bot, please reach out to us via the mailing list or GitHub
41
40
The bots are logging a deprecation warning now and the current plan is to remove them in IntelMQ version 3.0.
42
41
43
42
#### Shadowserver Bots
44
-
The Shadowserver Collector is now able to collect data from the [Shadowserver Reports API](https://intelmq.readthedocs.io/en/latest/user/bots.html#shadowserver-reports-api). Moreover the Shadowserver Parser now supports the JSON format used by the Reports API.
43
+
The Shadowserver Collector is now able to collect data from the [Shadowserver Reports API](https://intelmq.readthedocs.io/en/maintenance/user/bots.html#shadowserver-reports-api). Moreover the Shadowserver Parser now supports the JSON format used by the Reports API.
45
44
46
45
#### Sieve Expert
47
46
Sieve-Expert is now capable of basic math operations & you can do actions without any `if` statements.
@@ -51,16 +50,14 @@ Sieve-Expert is now capable of basic math operations & you can do actions withou
51
50
add time.observation += '1 hour'
52
51
add time.observation -= '10 hours'
53
52
```
54
-
2. Actions can now be used without an `if` statement, just write the following into a `.sieve` file
53
+
2. Actions can now be used without an `if` statement, just write the following into a `.sieve` file:
55
54
```
56
55
add comment = "Adding this to all computed events"
57
56
```
58
-
More details can be found in our [documentation](https://intelmq.readthedocs.io/en/latest/user/bots.html#sieve).
57
+
More details can be found in our [documentation](https://intelmq.readthedocs.io/en/maintenance/user/bots.html#sieve).
59
58
60
59
#### Kafka Collector
61
-
Now you're able to fetch data from Kafka with the [Kafka Collector](https://intelmq.readthedocs.io/en/latest/user/bots.html#kafka).
62
-
63
-
### Harmonization
60
+
Now you're able to fetch data from Kafka with the [Kafka Collector](https://intelmq.readthedocs.io/en/maintenance/user/bots.html#kafka).
64
61
65
62
### Configuration
66
63
#### Abuse.ch URLHaus feed
@@ -69,12 +66,10 @@ The correct name for the parameter "delimeter" is "delimiter". Please fix your c
69
66
The `intelmqctl upgrade-config` command automatically fixes a configuration if the misspelling is detected.
70
67
71
68
#### IntelMQ-Manager -> IntelMQ-API
72
-
`IntelMQ-Manager` PHP backend is getting replaced by the newly developed `IntelMQ-API`. The `IntelMQ-Manager` release only contains the files for the web frontend. The `IntelMQ-Manager` packages now depend or recommend the installation of the `IntelMQ-API` package, therefore a normal upgrade should pull in the API. Follow the instructions in our [documentation](https://intelmq.readthedocs.io/en/latest/user/intelmq-api.html) to configure the API. It uses its own authentication backend now, how to setup users is described in the [documentation](https://intelmq.readthedocs.io/en/latest/user/intelmq-api.html#adding-a-user).
73
-
74
-
### Libraries
69
+
`IntelMQ-Manager` PHP backend is getting replaced by the newly developed `IntelMQ-API`. The `IntelMQ-Manager` release only contains the files for the web frontend. The `IntelMQ-Manager` packages now depend or recommend the installation of the `IntelMQ-API` package, therefore a normal upgrade should pull in the API. Follow the instructions in our [documentation](https://intelmq.readthedocs.io/en/maintenance/user/intelmq-api.html) to configure the API. It uses its own authentication backend now, how to setup users is described in the [documentation](https://intelmq.readthedocs.io/en/maintenance/user/intelmq-api.html#adding-a-user).
75
70
76
71
### Postgres databases
77
-
There was a spelling error in the Spamhaus CERT parser's "event_description.text" texts.
72
+
There was a spelling error in the Spamhaus CERT Parser's "event_description.text" texts.
78
73
The following statements optionally update existing data.
79
74
Please check if you did use these feed names and eventually adapt them for your setup!
0 commit comments