Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.4.111 Changes #125

Merged
merged 22 commits into from
Dec 18, 2024
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
93caed8
Merge pull request #97 from Security-Onion-Solutions/dev
dougburks May 29, 2024
a989a92
Merge pull request #98 from Security-Onion-Solutions/dev
dougburks May 30, 2024
ac0e365
Merge pull request #99 from Security-Onion-Solutions/dev
dougburks May 31, 2024
44e1ad3
Merge pull request #101 from Security-Onion-Solutions/dev
dougburks May 31, 2024
980ac40
Merge pull request #102 from Security-Onion-Solutions/dev
dougburks Jun 4, 2024
f67a8f3
Merge pull request #103 from Security-Onion-Solutions/dev
dougburks Jun 10, 2024
3acbc48
Merge pull request #105 from Security-Onion-Solutions/dev
dougburks Jun 25, 2024
42d89b9
Merge pull request #108 from Security-Onion-Solutions/dev
TOoSmOotH Jul 29, 2024
f976681
Merge pull request #109 from Security-Onion-Solutions/dev
dougburks Jul 29, 2024
8a182df
Merge pull request #110 from Security-Onion-Solutions/dev
TOoSmOotH Aug 29, 2024
b363899
Merge pull request #112 from Security-Onion-Solutions/dev
dougburks Sep 3, 2024
9d422d6
Merge pull request #115 from Security-Onion-Solutions/dev
jertel Oct 7, 2024
929048f
Merge pull request #116 from Security-Onion-Solutions/dev
dougburks Oct 10, 2024
579c0b7
Merge pull request #117 from Security-Onion-Solutions/dev
dougburks Oct 10, 2024
c7eef0f
Merge pull request #120 from Security-Onion-Solutions/dev
dougburks Oct 18, 2024
03dd1e6
Merge pull request #121 from Security-Onion-Solutions/dev
dougburks Oct 18, 2024
4f6ead7
update release notes for 2.4.111
jertel Dec 16, 2024
7d2dd18
update release notes for 2.4.111
jertel Dec 16, 2024
d1d433f
update release notes for 2.4.111
jertel Dec 16, 2024
9e7a021
remove markdown syntax
jertel Dec 16, 2024
75fe4e9
Merge pull request #124 from Security-Onion-Solutions/patch/2.4.111
TOoSmOotH Dec 18, 2024
2e260f3
Merge branch 'dev' into merger
TOoSmOotH Dec 18, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions release-notes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,18 @@ Release Notes
Known Issues
~~~~~~~~~~~~

Salt Repo Location Changed
--------------------------

Salt is an external project used by Security Onion. After 2.4.100 was released the maintainers of Salt changed the package repository URL, which prevents Security Onion from installing on unsupported operating systems.

While we are looking to update Security Onion to use the new URL in the next minor release of Security Onion, this issue persists with the 2.4.111 patch. We recommend installing Security Onion using the ISO image to avoid these network installation and unsupported operating system complications.

If you choose to continue installing on an unsupported operating system you can consider applying the fix manually, as shown in this PR: https://github.com/Security-Onion-Solutions/securityonion/pull/13900


IP Address Data Type Conflict
-----------------------------
If you had previously updated to version 2.4.100 and had indices with conflicting data types for fields like source IP address, then you may need to delete affected indices. Field conflicts typically occur when a field is indexed using a different set of mappings than other indices. This can occur if a component template or index template changes and a data stream rolls over to create a new backing index, causing issues with field value aggregation and data tables not being rendered as expected.

Field conflicts can be identified by navigating to ``Kibana -> Management -> Data Views -> logs-*``. They are typically noted via a yellow banner on the data view page, or they can be found by filtering by a field type of ``conflict``. For each affected field, clicking the yellow ``Conflict`` icon in the ``Type`` column will display the conflicting field types and indices.
Expand Down Expand Up @@ -44,6 +56,14 @@ Then, delete the previous index for each of the affected data streams:

Finally, check the ``logs-*`` data view to see if the field conflict is now resloved.

Release History
~~~~~~~~~~~~~~~

2.4.111 Patch [20241217] Changes
--------------------------------

- UPGRADE: Suricata 7.0.8 `#14024 <https://github.com/Security-Onion-Solutions/securityonion/issues/14024>`_

2.4.110 Hotfix [20241010] Changes
---------------------------------

Expand Down
Loading