Giter Site home page Giter Site logo

Comments (4)

FloatingGhost avatar FloatingGhost commented on September 25, 2024

Your two snippets display different code being run, would I be correct in assuming you changed the script yourself?

config["taxii"]["auth"]["username"] is the correct config path

Provided you have your environment variables set as per the README and haven't changed the structure of the config file or amended the script, it will find the key.

The script itself does not need amending

Edit: You have two conflicting installs, one is going from a version at /usr/local/bin/ and the other somewhere indeterminate. Nonetheless I believe you edited the second one and changed the config path as it does not match the currently commited version

from misp-taxii-server.

faustus25 avatar faustus25 commented on September 25, 2024

Wait, there would need to be 2 config yaml files referenced to OPENTAXII_CONFIG (config.default.yaml and config.travis.yaml)

"run-taxii-poll.py" works when referencing config.default.yaml or config.yaml as you describe in the README:

Now, with that data, copy config/config.default.yaml over to config/config.yaml and open it

BUT in order to run "push_published_to_taxii.py", you need to update/use config.travis.yaml instead and then update the OPENTAXII_CONFIG to this yaml file which doesn't include the "Collections" section like in config.default.yaml

Checked there and that "push_published_to_taxii.py" works when OPENTAXII_CONFIG=~/config.travis.yaml

It would be better to have 2 separate OPENTAXII_CONFIGs referenced, one unique to each script CONFIG1 & CONFIG2

OPENTAXII_CONFIG1=/config.default.yaml
OPENTAXII_CONFIG2=
/config.travis.yaml

from misp-taxii-server.

FloatingGhost avatar FloatingGhost commented on September 25, 2024

I think you've misinterpreted my comments

The comment in #4 was because config.default.yaml did not yet exist. The config.travis.yaml file is solely for travis CI, and is not a config file for you to use.

You should be using one singular file at config.yaml, which should be based on config.default.yaml, which is why I say to copy it. It's a skeleton config.

from misp-taxii-server.

faustus25 avatar faustus25 commented on September 25, 2024

Therein lies the issue: "config.yaml" (config.default.yaml) works with "run-taxii-poll.py" (without modification) while config.travis.yaml (without modification) works with "push_published_to_taxii.py.

In any case, I will use config.yaml solely for "run-taxii-poll.py".

from misp-taxii-server.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.