Connectivity Errors when trying to test a scan on "Dependency Check CLI"

[diopha...@gmail.com]

I am trying to use the dependency check cli on my Ubuntu 14.04 and doing some example testing, I followed the instructions on http://jeremylong.github.io/DependencyCheck/dependency-check-cli/index.html but I still can't run a basic test scan.

Here are the commands I ran:

user:~/DepCheck$ cd dependency-check/bin

user:~/DepCheck/dependency-check/bin$ ls

dependency-check.bat  dependency-check.sh

user:~/DepCheck/dependency-check/bin$ chmod 777 dependency-check.sh

chmod: changing permissions of ‘dependency-check.sh’: Operation not permitted

user:~/DepCheck/dependency-check/bin$ sudo chmod 777 dependency-check.sh

[sudo] password for user: 

user:~/DepCheck/dependency-check/bin$ ./dependency-check.sh --project Testing --out . --scan /home/user/Documents/project

[ERROR] Unable to connect to the dependency-check database; analysis has stopped

user:~/DepCheck/dependency-check/bin$ 

[Jeremy Long]

Any follow-up to this request for assistance can be found here: https://github.com/jeremylong/DependencyCheck/issues/532

--
You received this message because you are subscribed to the Google Groups "Dependency Check" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dependency-che...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Max Allan]

You have a fundamental permission problem

user:~/DepCheck/dependency-check/bin$ chmod 777 dependency-check.sh

chmod: changing permissions of ‘dependency-check.sh’: Operation not permitted

This was the clue that the current user has no permissions to files in the current directory.

user:~/DepCheck/dependency-check/bin$ ./dependency-check.sh --project Testing --out . --scan /home/user/Documents/project

[ERROR] Unable to connect to the dependency-check database; analysis has stopped

user:~/DepCheck/dependency-check/bin$ 

So the dependency check probably cannot create the out directory in the current location because it doesn't have permission. 
The fact that you have sudo permission on this server worries me when you have such a limited grasp of what is going on. I suggest you look at a tutorial about unix file permissions before you continue breaking your server.