[297] | 1 | to 2.8.0 and higher: samhain supports IPv6 now, which means that the
|
---|
| 2 | size of the 'ip' column in the database must be increased from
|
---|
| 3 | VARCHAR(16) to VARCHAR(46).
|
---|
[27] | 4 |
|
---|
[297] | 5 | BE SURE TO MAKE A BACKUP BEFORE THIS!
|
---|
| 6 |
|
---|
| 7 | -- mysql: alter table samhain.log modify ip VARCHAR(46);
|
---|
| 8 |
|
---|
| 9 | -- postgresql: alter table samhain.log alter column ip type varchar(46);
|
---|
| 10 |
|
---|
| 11 | -- oracle: alter table samhain.log modify ip VARCHAR2(46);
|
---|
| 12 |
|
---|
| 13 |
|
---|
[170] | 14 | to 2.4.4 and higher: it is possible now to store the full content of
|
---|
| 15 | small files in the baseline database. To support this feature with
|
---|
| 16 | logging to an RDBMS, the DB schema for Oracle needs to be adjusted
|
---|
| 17 | by converting the link_old, link_new columns from VARCHAR2 to CLOB:
|
---|
| 18 |
|
---|
| 19 | -- Oracle:
|
---|
| 20 | ALTER TABLE samhain.log ADD tmp_name CLOB;
|
---|
| 21 | UPDATE samhain.log SET tmp_name=link_old;
|
---|
| 22 | ALTER TABLE samhain.log DROP COLUMN link_old;
|
---|
| 23 | ALTER TABLE samhain.log RENAME COLUMN tmp_name to link_old;
|
---|
| 24 |
|
---|
| 25 | ALTER TABLE samhain.log ADD tmp_name CLOB;
|
---|
| 26 | UPDATE samhain.log SET tmp_name=link_new;
|
---|
| 27 | ALTER TABLE samhain.log DROP COLUMN link_new;
|
---|
| 28 | ALTER TABLE samhain.log RENAME COLUMN tmp_name to link_new;
|
---|
| 29 |
|
---|
| 30 | -- Samhain server (yule): if you are logging to the RDBMS via
|
---|
| 31 | the server (yule), as recommended, you need to also upgrade the
|
---|
| 32 | server, because earlier versions had a too restrictive limit on
|
---|
| 33 | the maximum length of an SQL query.
|
---|
| 34 |
|
---|
| 35 |
|
---|
[93] | 36 | to 2.3.3 and higher: a bug has been fixed that resulted in an additional
|
---|
| 37 | slash at the beginning of the linked path of symlinks in the root
|
---|
| 38 | directory (symlinks in other directories were not affected)
|
---|
[68] | 39 |
|
---|
[93] | 40 | -- this may cause spurious warnings about modified links, if you check
|
---|
| 41 | against a database created with an earlier version of samhain
|
---|
| 42 |
|
---|
| 43 |
|
---|
| 44 |
|
---|
| 45 | from lower to 2.3.x: the database scheme has changed slightly.
|
---|
| 46 | To upgrade, use the following SQL commands in the command-line
|
---|
| 47 | client of your database:
|
---|
| 48 |
|
---|
[68] | 49 | -- MySQL:
|
---|
| 50 | ALTER TABLE samhain.log ADD COLUMN acl_old BLOB;
|
---|
| 51 | ALTER TABLE samhain.log ADD COLUMN acl_new BLOB;
|
---|
| 52 |
|
---|
| 53 | -- PostgreSQL:
|
---|
| 54 | ALTER TABLE samhain.log ADD COLUMN acl_old TEXT;
|
---|
| 55 | ALTER TABLE samhain.log ADD COLUMN acl_new TEXT;
|
---|
| 56 |
|
---|
| 57 | -- Oracle:
|
---|
[73] | 58 | ALTER TABLE samhain.log ADD acl_old VARCHAR2(4000);
|
---|
| 59 | ALTER TABLE samhain.log ADD acl_new VARCHAR2(4000);
|
---|
[68] | 60 | DROP TRIGGER trigger_on_log;
|
---|
| 61 |
|
---|
| 62 |
|
---|
| 63 |
|
---|
[27] | 64 | since 2.2.0: server-to-server relay is possible
|
---|
| 65 |
|
---|
| 66 | -- this implies that problems will arise if your server is misconfigured
|
---|
| 67 | to connect to itself (SetExportSeverity is explicitely set
|
---|
| 68 | to a threshold different from 'none', and the logserver is set to
|
---|
| 69 | localhost). The server may deadlock in this case.
|
---|
| 70 |
|
---|
| 71 |
|
---|
| 72 |
|
---|
[18] | 73 | since 2.1.0: update and daemon mode can be combined
|
---|
[1] | 74 |
|
---|
[18] | 75 | -- this implies that '-t update' will start a daemon process if running as
|
---|
| 76 | daemon is the default specified in the config file. use '--foreground'
|
---|
| 77 | to avoid starting a daemon process
|
---|
| 78 |
|
---|
| 79 |
|
---|
| 80 |
|
---|
[1] | 81 | from 1.7.x to 1.8.x: client/server encryption protocol has been enhanced
|
---|
| 82 |
|
---|
| 83 | -- 1.7.x clients can connect to a 1.8.x server
|
---|
| 84 |
|
---|
| 85 | -- 1.8.x clients can only connect to a 1.7.x server, if they
|
---|
| 86 | are built with --enable-encrypt=1
|
---|
| 87 |
|
---|
| 88 |
|
---|
| 89 |
|
---|
| 90 | from 1.6.x to 1.7.x: things to watch out for
|
---|
| 91 |
|
---|
| 92 | -- the log server drops root privileges after startup; it needs a logfile
|
---|
| 93 | directory with write access for the unprivileged user now
|
---|
| 94 |
|
---|
| 95 | -- the PID file does not double as lock for the log file anymore; the
|
---|
| 96 | log file has its own lock now (same path, with .lock appended)
|
---|
| 97 |
|
---|
| 98 | -- by default, the HTML status page of the server is in the log directory
|
---|
| 99 | now; this allows to make the data directory read-only for the server
|
---|
| 100 |
|
---|