Allow for longer entries in the system.information column #802
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Switch from VARCHAR(128) to TEXT to allow for longer entries in the
information column. On server registration, this column is typically
loaded with the output of ```uname -a```. That's frequently longer than
128 characters. For instance on the FreeBSD servers I manage, it's
typically in excess of 180 characters:
```
ox-dell39:~:% uname -a | wc
1 15 185
```
Since the length of the data being written to that column is not
checked, this results in a failed SQL query at which the ossec-dbd
process quits.
Tested with postgresql; equivalent change applied to mysql.schema
but not tested.
|
How does this change affect current installations/upgrades? |
|
On 04/14/16 13:00, Dan Parriott wrote:
This should only ever affect new installs. Anyone already using the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch from VARCHAR(128) to TEXT to allow for longer entries in the
information column. On server registration, this column is typically
loaded with the output of
uname -a. That's frequently longer than128 characters. For instance on the FreeBSD servers I manage, it's
typically in excess of 180 characters:
Since the length of the data being written to that column is checked,
this results in a failed SQL query at which the ossec-dbd process quits.
Tested with postgresql; equivalent change applied to mysql.schema