From 4533049b92b6dcb1e24e6405e61274fdd695b70a Mon Sep 17 00:00:00 2001 From: iglocska Date: Tue, 21 Jan 2020 11:30:00 +0100 Subject: [PATCH] fix: gremar fikses --- _posts/2020-01-21-MISP.2.4.120.released.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/_posts/2020-01-21-MISP.2.4.120.released.md b/_posts/2020-01-21-MISP.2.4.120.released.md index e50954e..7b4b3aa 100644 --- a/_posts/2020-01-21-MISP.2.4.120.released.md +++ b/_posts/2020-01-21-MISP.2.4.120.released.md @@ -6,35 +6,35 @@ featured: /assets/images/misp/blog/t-misp-overview.png # MISP 2.4.120 released -A new version of MISP ([2.4.120](https://github.com/MISP/MISP/tree/v2.4.120)) has been released, including an extension to the data-model which adds first_seen and last_seen values at attribute and object level. The user-interface has been extended with a timeline view/editor per event to see all the occurrences of attributes and objects based on their time. A new quick object edit function has been added to easily add new attributes. Many bugs were fixed and also various improvement were made in the existing features. +A new version of MISP ([2.4.120](https://github.com/MISP/MISP/tree/v2.4.120)) has been released, including an extension to the data-model adding the first_seen and last_seen values at the attribute and object levels. The user-interface has been extended with a timeline view/editor per event, allowing users to see all occurrences of attributes and objects based on time. A new quick object edit tool has been added, enabling users to easily add new attributes to already existing objects. A long list of bugs were fixed and various improvements were made in the existing features. # Update notes -Don't forget to have the workers running before doing the update, there are some updates on the database which can take time depending of the size of the your MISP instance. The -progress of the update can be verified on the interface of your MISP instance at the following location /servers/updateProgress . +Don't forget to have background workers running before updating, there are some updates to the database which can take time depending on the size of your MISP instance. The +progress of the update can be verified via the interface of your MISP instance using the following endpoint: /servers/updateProgress . # Timeline feature and improved data-model