Skip to content
This repository has been archived by the owner on Apr 26, 2021. It is now read-only.

Provide a centralized place to handle Options definitions #547

Open
jpsenior opened this issue May 12, 2015 · 6 comments
Open

Provide a centralized place to handle Options definitions #547

jpsenior opened this issue May 12, 2015 · 6 comments
Labels

Comments

@jpsenior
Copy link
Contributor

As some of the increased demands for cuckoo grow, more option requests are being added to support various new features.
It would be helpful to centralize these options and their definitions to reference them in multiple places: e.g. submit.py, database add, API, web interface.
A warning should be sent to the user if they are using a cuckoo option that is not supported.

I'll write a small patch for this small issue myself, just putting a ticket in to track it somewhere.

@jbremer
Copy link
Member

jbremer commented Jun 4, 2015

@jpsenior Did you end up doing any code for this feature? :)

@botherder
Copy link
Member

I don't think I fully understand the purpose of that. The options for the analysis packages should be tracked in the documentation. You want to extract them from there and have the submission interfaces make sure they are correct?

@jbremer
Copy link
Member

jbremer commented Jun 6, 2015

Yes.

@jpsenior
Copy link
Contributor Author

jpsenior commented Jun 8, 2015

Apologies, life with newborn babies...

@botherder
Copy link
Member

Any updates on the patch?

@LisaBananapai
Copy link

@jpsenior Did you end up doing any code for this feature? :)

I want to contact with you. Does cuckoo can do static analysis?Though I success to construct it, I can’t get more static analysis information from it after I have tests many samples.

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

No branches or pull requests

5 participants
@botherder @jbremer @jpsenior @LisaBananapai and others