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

unable to unmarshal: wappalyzer schema definition file changed #7

Closed
francisco-sec opened this issue Aug 10, 2017 · 3 comments
Closed
Assignees

Comments

@francisco-sec
Copy link

I installed your tool like described in the README (in Arch Linux) and it keeps giving this error below:

$ go run cmd/webanalyze/main.go -host https://host/path/ 
2017/08/10 16:24:18 error initializing: json: cannot unmarshal number into Go struct field App.cats of type string

Is this normal? After the previous error the execution seems to proceed but hang.

2017/08/10 16:24:18 Scanning with 4 workers.
@rverton rverton self-assigned this Aug 11, 2017
@rverton
Copy link
Owner

rverton commented Aug 11, 2017

Thanks for the notice. It looks like the schema of the apps.json file from webanalyze changed again. I will check this.

@rverton rverton changed the title Error when running webanalyze unable to unmarshal: webalizer schema definition file changed Aug 11, 2017
@rverton rverton changed the title unable to unmarshal: webalizer schema definition file changed unable to unmarshal: wappalyzer schema definition file changed Aug 11, 2017
@rverton
Copy link
Owner

rverton commented Aug 11, 2017

So the problem is that wappalyzer is not very .. strict on their apps.json schema. Have a look at how the usually define their categories, for example:

"cats": [
    "20",
    "51"
],

And now look at this:

"cats": [
    1
],

This fails to unmarshal, because I am expecting a string, and not a number. To fix this you can do this by hand (change 1 to "1"). I will also prepare a PR for the wappalyzer repository.

Update: You can track the PR here.

@rverton rverton closed this as completed Aug 11, 2017
@francisco-sec
Copy link
Author

Many thanks you for your quick answer. I made that change in my local apps.json and it works now.

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

2 participants