Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-root user can no longer use secure build #24

Open
silliman opened this issue Dec 20, 2021 · 0 comments
Open

Non-root user can no longer use secure build #24

silliman opened this issue Dec 20, 2021 · 0 comments

Comments

@silliman
Copy link
Contributor

It appears that the recent commit 284c177 requires that a hostname for the secure build server be specified as part of the secure build process, and then the user must update the /etc/hosts file on the system that they use for running the secure build CLI.

If a user does not have root access on their system then they will not be able to update the /etc/hosts file and will not be able to successfully execute secure build CLI commands. For example, in such an environment, where I cannot update /etc/hosts, attempting

./build.py status --env sbs-config.json --noverify

returns this error

INFO:__main__:build: status NewConnectionError e=HTTPSConnectionPool(host='sbs.barry.com', port=443): Max retries exceeded with url: /image (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fd890300370>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

I would prefer to have the option to not require a hostname so that non-root users (or, to be more precise, users without the ability to update /etc/hosts on their system) can use the secure build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant