-
Notifications
You must be signed in to change notification settings - Fork 5
csirtgsdk submission with token #141
Comments
happy to accept pull requests- we tried that early on but envvars are bit more flexible.. have you tried modifying os envvar before csirtgsdk is pulled in? that said- starting to simplify the sdk a little with a v2: https://github.com/csirtgadgets/csirtgsdk-py-v2 maybe we can make that a little easier depending on what you're trying to do? |
I tried to change the environment variable already but couldn't make it work. So the variable is read at the moment of import of the csirtgsdk module? That could explain it, because my imports come before the rest of the logic (setting the env. variable). All i'm trying to do is to submit an indicator to csirtg through a cowrie output module. I think you wrote the original |
Yeah confirmed the TOKEN variable is set upon module loading. The client can receive a TOKEN through a named variable, but the Indicator object doesn't seem to take the client object. It's documented as a parameter, but the documentation doesn't seem to reflect reality. Why not do it like this:
becomes:
I was a bit confused by the kwargs, is this intended to be **kwargs? Or is it expecting a dictionary as input? because **kwargs turns named arguments into a dictionary, but that's mostly a naming convention. |
Hi.
I'm trying to update the csirtgsdk module in Cowrie.
I'm using
and then (abbreviated):
The Indicator() doesn't seem to take the client object.
I'd rather not use environment variable CSIRTG_TOKEN but pass it into the client object.
How do i submit an indicator with a custom client object?
regards,
Michel.
The text was updated successfully, but these errors were encountered: