Bug #2921: chmod file mode warning expressed in incorrect base - Suricata - Open Information Security Foundation

Actions

Copy link

Bug #2921

closed

chmod file mode warning expressed in incorrect base

Added by Emmanuel Roullit about 5 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Emmanuel Roullit

Target version:

5.0beta1

Affected Versions:

Effort:

Difficulty:

low

Label:

Description

I have configure suricata to open the output file with filemode 664.
On file rotation, I could see this warning:

[2824] 5/4/2019 -- 10:30:00 - (util-logopenfile.c:289) <Warning> (SCLogOpenFileFp) -- [ERRCODE: SC_WARN_CHMOD(297)] - Could not chmod logs/eve.json to 436: Operation not permitted

At first glance, it does not look like the file mode I have configured because it is printed in base 10. Where this number in base 8 is 0664.

$ python
>>> oct(436)
'0664'
>>>

I have prepared a changeset which correct that and on logrotate, the printed warning is:

[11586] 5/4/2019 -- 10:41:02 - (util-logopenfile.c:289) <Warning> (SCLogOpenFileFp) -- [ERRCODE: SC_WARN_CHMOD(297)] - Could not chmod logs/eve.json to 664: Operation not permitted