soup: handle situations where apt prompts to keep/replace file

[dougburks]

Occasionally Ubuntu releases updates which will prompt the user to keep or replace a file. During a normal interactive soup, the user can answer the prompt and everything is fine. However, if the user runs sudo salt '*' cmd.run 'soup -y', then the salt minion runs soup -y and it will most likely just hang there waiting for user input.

[weslambert]

Maybe something like https://debian-handbook.info/browse/stable/sect.package-meta-information.html#sidebar.questions-conffiles ?

[dougburks]

Yes, but we need to make sure we understand the behavior and how it applies to at least these two separate cases:

1. This discussion started when Phil mentioned a recent example of unattended-upgrades. In this example, it's probably safe to accept the default and allow the new version of the file to be installed.

2. Suppose a user modifies some Ubuntu file in /etc, then Ubuntu upgrades the package, and it overwrites their changes. At the very least, the user needs to know that the file was overwritten so that they can reapply their custom changes.

This will require some testing and experimentation to see if there are any other corner cases out there.

[dougburks]

commits:
Security-Onion-Solutions/securityonion-sostat@e116b81
Security-Onion-Solutions/securityonion-sostat@8f8f55d

[dougburks]

submitted for testing:
https://groups.google.com/d/topic/security-onion-testing/-PAX_MBFj18/discussion

[dougburks]

published:
http://blog.securityonion.net/2017/08/securityonion-sostat-20120722.html