Update README.md for umask.

[jboero]

Build requires a umask 0022 which isn't the default in current security-focused enterprise distributions.

Description

Screenshots (if appropriate)

How to Test

Checklist

• [ ] I have added before and after screenshots for UI changes
• [ ] I have added JSON response output for API changes
• [ ] I have added steps to reproduce and test for bug fixes in the description
• [ ] I have commented on my code, particularly in hard-to-understand areas
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
boundary-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 17, 2024 10:38am
boundary-ui-desktop	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 17, 2024 10:38am

[jboero]

The buid error hit with default umask 0027:

✔ Running preMake hook
❯ Making distributables
  ✖ Making a zip distributable for linux/x64
  ✖ Making a deb distributable for linux/x64
    › Command failed with a non-zero return code (2):
      fakeroot dpkg-deb --build /tmp/electron-installer--336252-oRY4NjWWu6G5/boundary-desktop_0.0.0_amd64
      dpkg-deb: error: control directory has bad permissions 750 (must be >=0755 and <=0775)
◼ Running postMake hook

An unhandled rejection has occurred inside Forge:
Error: Command failed with a non-zero return code (2):
fakeroot dpkg-deb --build /tmp/electron-installer--336252-oRY4NjWWu6G5/boundary-desktop_0.0.0_amd64

dpkg-deb: error: control directory has bad permissions 750 (must be >=0755 and <=0775)
at ChildProcess.<anonymous> (/home/jboero/code/boundary-ui/ui/desktop/electron-app/node_modules/electron-installer-debian/node_modules/@malept/cross-spawn-promise/dist/src/index.js:99:24)
    at ChildProcess.emit (node:events:518:28)
    at ChildProcess.emit (node:domain:488:12)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[cameronperera]

Thanks for your input. We do not typically accept these type of PRs as they do not apply to our internal build process. However, we are happy to add a note that users will need full permissions to build the desktop client locally. Again, we appreciate your input.

[cameronperera]

PR with comment about needing full permissions when building the desktop client