Jens Schmalzing <jens.schmalzing@physik.uni-muenchen.de> writes: > The config script assumes it can clobber the file if a configuration > file *either* does not exist *or* its MD5 fingerprint is identical to > an MD5 fingerprint stored by a previous invocation of the postinst > script. If it may clobber the file, it asks a number of questions and > stores the answers in debconf. Otherwise, it informs the user that > the file will be left alone. > > The postinst script again checks whether it is allowed to clobber the > file and if this is the case, creates the file based on the debconf > answers. What happens if the admin decides to delete the file in the time window between config and postinst runs? So that the first clobber check fails, and the second one succeeds? -- Robbe
Attachment:
signature.ng
Description: PGP signature