From: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: build failing with default umask changed from 0022 to 0077
Date: Thu, 26 Oct 2023 11:49:54 +0000 [thread overview]
Message-ID: <PAWPR10MB71747431E98CC2544009EFE0FBDDA@PAWPR10MB7174.EURPRD10.PROD.OUTLOOK.COM> (raw)
Hello,
Some security measures require the default umask to be changed from 0022 to 0077
This causes Isar builds to fail as we often create files with default (unspecified) permissions and are switching between privileged (sudo) and regular accounts ($USER)
Would you like us to be fixing such problems?
Should we instead recommend the user to umask 0022 prior to starting his build?
Thanks
Cedric
next reply other threads:[~2023-10-26 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:49 cedric.hombourger [this message]
2023-10-27 8:45 ` Uladzimir Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PAWPR10MB71747431E98CC2544009EFE0FBDDA@PAWPR10MB7174.EURPRD10.PROD.OUTLOOK.COM \
--to=cedric.hombourger@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox