Suricata » Suricata-Update

This isn't something we see coming up in generate usage of Suricata-Update so I'm not sure about the priority. Plus, needing to move in files for datasets, and md5's (https://redmine.openinfosecfoundation.org/issues/2688) are going to complicate things.

I wonder if the answer is to drop a cookie. When running, if the output directory does not exist, create it, and drop a cookie file (.suricata-update). If its empty, drop the cookie file. Otherwise check if the cookie exists, and refuse to run if not with a meaningful error message.

I wonder if the answer is to drop a cookie. When running, if the output directory does not exist, create it, and drop a cookie file (.suricata-update). If its empty, drop the cookie file. Otherwise check if the cookie exists, and refuse to run if not with a meaningful error message.

This makes sense. Should this work be carried on or dropped or halted till #2688 is addressed?

Shivani Bhardwaj wrote:

I wonder if the answer is to drop a cookie. When running, if the output directory does not exist, create it, and drop a cookie file (.suricata-update). If its empty, drop the cookie file. Otherwise check if the cookie exists, and refuse to run if not with a meaningful error message.

This makes sense. Should this work be carried on or dropped or halted till #2688 is addressed?

Lets hold off until #2688 is addressed.