Suricata » Suricata-Update

suricata-update should be more clear about permission problems. Here I ran suricata-update as a regular user:

 victor   master  ~  devel  suricata-update  ./bin/suricata-update 
20/12/2017 -- 12:42:22 - <Warning> -- No suricata application binary found on path.
20/12/2017 -- 12:42:22 - <Info> -- Using default Suricata version of 4.0.0
20/12/2017 -- 12:42:22 - <Error> -- Source index is required for source oisf/trafficid; run suricata-update update-sources
 victor   master  ~  devel  suricata-update  1  ./bin/suricata-update update-sources
20/12/2017 -- 12:42:29 - <Warning> -- No suricata application binary found on path.
20/12/2017 -- 12:42:29 - <Info> -- Using default Suricata version of 4.0.0
20/12/2017 -- 12:42:29 - <Info> -- Downloading https://www.openinfosecfoundation.org/rules/index.yaml
Traceback (most recent call last):
  File "./bin/suricata-update", line 26, in <module>
    sys.exit(main.main())
  File "/home/victor/sync/devel/suricata-update/suricata/update/main.py", line 1372, in main
    sys.exit(_main())
  File "/home/victor/sync/devel/suricata-update/suricata/update/main.py", line 1149, in _main
    return args.func()
  File "/home/victor/sync/devel/suricata-update/suricata/update/commands/updatesources.py", line 50, in update_sources
    with open(local_index_filename, "wb") as outobj:
IOError: [Errno 13] Permission denied: '/var/lib/suricata/update/cache/index.yaml'

Note that the first 'update' command doesn't give any useful feedback.

The suggested 'update-sources' fails predictably, but with an ugly backtrace instead of a pretty error.