Wrong permissions on intermediary directories leading to a file

[https://www.google.com/accounts/o8/id?id=AItOawlmQQXfSG8MiJbq8L5pwwSZpPJqtMfKtG8]

Seen on bcfg2-1.3.0pre[12]:

If a <Path/> entry defines a file in a directory path that does not exist yet, bcfg2 creates the directory path leading to the file, but with inadequate permissions. For instance, for: <Path name="/foo/bar/baz"/> directories /foo and /foo/bar will be created with owner:permissions root:root:0644. On some systems I've seen directories created with permissions 0744 which makes me think this may be related to umask inheritance.

This is similar, but not quite the same, as ticket 1125

[https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc]

Fixed in ​https://github.com/Bcfg2/bcfg2/commit/10eb7f52b799e6b36deeebb9b78f5d0734d9f05b