Bug#767390: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade

2014-10-31 Thread Dominik George
I think this patch doesn't work when installing a new package (it does work on upgrades). So I think the two added lines need to be within an 'if [ -e $outputfile ] ; then' statement. I figured that and re-created the patch - apparently, I uploaded the old one :(. Turns out it is not

Bug#767390: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade

2014-10-31 Thread Paul Gevers
On 31-10-14 12:35, Dominik George wrote: I think this patch doesn't work when installing a new package (it does work on upgrades). So I think the two added lines need to be within an 'if [ -e $outputfile ] ; then' statement. I figured that and re-created the patch - apparently, I uploaded

Bug#767390: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade

2014-10-31 Thread Dominik George
mktemp is supposed to be secure, catting into a yet non-existing file may not. Paul mktemp is safe in that it uses unique file names. Apart from that it adheres to the effective user and effective umask, making it no more and no less safe than any other operation creating files. -nik --

Bug#767390: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade

2014-10-31 Thread Julien Cristau
On Fri, Oct 31, 2014 at 12:59:06 +0100, Dominik George wrote: mktemp is supposed to be secure, catting into a yet non-existing file may not. Paul mktemp is safe in that it uses unique file names. Apart from that it adheres to the effective user and effective umask, making it no more