You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rita runs under sudo, so it should be able to access any file on the system. Instead, when handed a directory of log files with mode 600 it returns "no valid log files found". (Confirmed that when the log files modes are changed to 644 the rita import command runs successfully and builds the database.)
Command used: rita import --database pi_zeek_2024_04_29 -l /home/wstearns/pi_zeek/2024-04-29/
Version tested: 5.0.8
The section in question appears to be
It's unclear to me why line 422 "_, err := afs.Open(path)" returns an error as rita running as root should be able to read this. Is it some oddity where it's running as root on the host but inside the docker container it's not (meaning the files truly are unreadable)?
Could we at least warn the user that the mode is the problem (and all files should be world readable) instead of saying "no valid log files found"?
The text was updated successfully, but these errors were encountered:
Rita runs under sudo, so it should be able to access any file on the system. Instead, when handed a directory of log files with mode 600 it returns "no valid log files found". (Confirmed that when the log files modes are changed to 644 the rita import command runs successfully and builds the database.)
Command used: rita import --database pi_zeek_2024_04_29 -l /home/wstearns/pi_zeek/2024-04-29/
Version tested: 5.0.8
The section in question appears to be
rita/cmd/import.go
Line 421 in 93b2dc5
It's unclear to me why line 422 "_, err := afs.Open(path)" returns an error as rita running as root should be able to read this. Is it some oddity where it's running as root on the host but inside the docker container it's not (meaning the files truly are unreadable)?
Could we at least warn the user that the mode is the problem (and all files should be world readable) instead of saying "no valid log files found"?
The text was updated successfully, but these errors were encountered: