nodejs-scanner failing on read permissions
Summary
nodejs-scanner has started failing on an issue with permissions when reading .ssh
, but its unclear why its trying to read this directory, as well.
Steps to reproduce
(How one can reproduce the issue - this is very important)
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
nodejs-scanner fails when trying to read .ssh
dir
What is the expected correct behavior?
nodejs-scanner wont fail when trying to read .ssh
dir
Relevant logs and/or screenshots
2: Pulling from gitlab-org/security-products/analyzers/nodejs-scan
a073c86ecf9e: Pulling fs layer
0e28711eb56d: Pulling fs layer
e460dd483fdd: Pulling fs layer
85ef67b3af78: Pulling fs layer
d0d5f67eed39: Pulling fs layer
2ff5cc335a21: Pulling fs layer
85ef67b3af78: Waiting
d0d5f67eed39: Waiting
2ff5cc335a21: Waiting
e460dd483fdd: Verifying Checksum
e460dd483fdd: Download complete
a073c86ecf9e: Verifying Checksum
a073c86ecf9e: Download complete
d0d5f67eed39: Verifying Checksum
d0d5f67eed39: Download complete
85ef67b3af78: Verifying Checksum
85ef67b3af78: Download complete
0e28711eb56d: Verifying Checksum
0e28711eb56d: Download complete
2ff5cc335a21: Verifying Checksum
2ff5cc335a21: Download complete
a073c86ecf9e: Pull complete
0e28711eb56d: Pull complete
e460dd483fdd: Pull complete
85ef67b3af78: Pull complete
d0d5f67eed39: Pull complete
2ff5cc335a21: Pull complete
Digest: sha256:c3a3e79d8e913303edc899f91eac980707e1bf901a013215e4f4a55518e336a0
Status: Downloaded newer image for registry.gitlab.com/gitlab-org/security-products/analyzers/nodejs-scan:2
Found project in /tmp/app
30 rules loaded
2019/09/19 14:36:30 open /tmp/app/tmp/tests/.ssh: permission denied
2019/09/19 14:36:31 Container exited with non zero status code
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)