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

README.md: Clarify that Toolbx isn't a security mechanism #1182

Merged
merged 3 commits into from
Nov 29, 2022

Conversation

debarshiray
Copy link
Member

@debarshiray debarshiray commented Nov 29, 2022

Using the word containerized gives the false impression of heightened security. As if it's a mechanism to run untrusted software in a sandboxed environment without access to the user's private data (such as $HOME), hardware peripherals (such as cameras and microphones), etc.. That's not what Toolbx is for.

Toolbx aims to offer an interactive command line environment for development and troubleshooting the host operating system, without having to install software on the host. That's all. It makes no promise about security beyond what's already available on the usual command line environment on the host that everybody is familiar with.

#1020

debarshiray added a commit to debarshiray/toolbox that referenced this pull request Nov 29, 2022
Mention that Toolbx is meant for system administrators to troubleshoot
the host operating system.  The word 'debugging' is often used in the
context of software development, and hence most readers might not
interpret it as 'troubleshooting'.

containers#1182
Mention that Toolbx is meant for system administrators to troubleshoot
the host operating system.  The word 'debugging' is often used in the
context of software development, and hence most readers might not
interpret it as 'troubleshooting'.

containers#1182
Using the word 'containerized' gives the false impression of heightened
security.  As if it's a mechanism to run untrusted software in a
sandboxed environment without access to the user's private data (such as
$HOME), hardware peripherals (such as cameras and microphones), etc..
That's not what Toolbx is for.

Toolbx aims to offer an interactive command line environment for
development and troubleshooting the host operating system, without
having to install software on the host.  That's all.  It makes no
promise about security beyond what's already available in the usual
command line environment on the host that everybody is familiar with.

containers#1020
@debarshiray
Copy link
Member Author

Is there a problem with GitHub? go mod download -x failed with:

ci-node-36 |       remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/alecthomas/kingpin.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
ci-node-36 |       fatal: unable to access 'https://gopkg.in/alecthomas/kingpin.v2/': The requested URL returned error: 502
ci-node-36 | go: unrecognized import path "gopkg.in/check.v1": reading https://gopkg.in/check.v1?go-get=1: 502 Bad Gateway
ci-node-36 |       server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-check/check.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
ci-node-36 | go: unrecognized import path "gopkg.in/errgo.v2": reading https://gopkg.in/errgo.v2?go-get=1: 502 Bad Gateway
ci-node-36 |       server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-errgo/errgo.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
ci-node-36 | go: gopkg.in/ini.v1@v1.66.2: invalid version: git ls-remote -q origin in /home/zuul-worker/go/pkg/mod/cache/vcs/b7879a4be9ba8598851b8278b14c4f71a8316be64913298d1639cce6bde59bc3: exit status 128:
ci-node-36 |       remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-ini/ini.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
ci-node-36 |       fatal: unable to access 'https://gopkg.in/ini.v1/': The requested URL returned error: 502
ci-node-36 | go: unrecognized import path "gopkg.in/yaml.v2": reading https://gopkg.in/yaml.v2?go-get=1: 502 Bad Gateway
ci-node-36 |       server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
ci-node-36 | go: unrecognized import path "gopkg.in/yaml.v3": reading https://gopkg.in/yaml.v3?go-get=1: 502 Bad Gateway
ci-node-36 |       server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

@debarshiray
Copy link
Member Author

recheck

@softwarefactory-project-zuul
Copy link

Build failed.

unit-test RETRY_LIMIT in 8m 07s
unit-test-migration-path-for-coreos-toolbox RETRY_LIMIT in 7m 52s
system-test-fedora-rawhide RETRY_LIMIT in 18m 43s
system-test-fedora-36 RETRY_LIMIT in 7m 51s
system-test-fedora-35 RETRY_LIMIT in 6m 41s

@debarshiray
Copy link
Member Author

recheck

@debarshiray debarshiray merged commit d0fe8c4 into containers:main Nov 29, 2022
@debarshiray debarshiray deleted the wip/rishi/issue-1020 branch November 29, 2022 19:06
@debarshiray
Copy link
Member Author

I keep getting the same network errors over and over again. :(

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

Successfully merging this pull request may close these issues.

1 participant