Related fdo#60338: do not call umask(3) in a MT program

...and it is unclear what this call was supposed to help for; if a user
deliberately sets its umask too strong, then better live with the consequences
than to silently "fix" it.

Change-Id: I0d84a7d1bd6f007794a65e1f7cc4ea09ebd9d4af