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

Multi-threaded code to upload the indicators into CRITs #88

Merged
merged 7 commits into from
Nov 18, 2014

Conversation

paulpc
Copy link
Contributor

@paulpc paulpc commented Oct 21, 2014

commented some of the functions, added the code to upload the indicators to CRITs with some parallel request capabilities (to maybe be replaced by grequests), and changed some of the code in combine.py to make it case-insensitive in the parsing of command line parameters.

@alexcpsec
Copy link
Member

Thanks for this, Paul! You think you can merge our current master back to your repo so this can be at least mergeable?

@paulpc
Copy link
Contributor Author

paulpc commented Oct 21, 2014

working on it - didn't notice all the logging work and the new version of
grequests

Paul Poputa-Clean

On Tue, Oct 21, 2014 at 3:53 PM, Alex Pinto notifications@github.com
wrote:

Thanks for this, Paul! You think you can merge our current master back to
your repo so this can be at least mergeable?


Reply to this email directly or view it on GitHub
#88 (comment).

@paulpc
Copy link
Contributor Author

paulpc commented Oct 21, 2014

ok, give this a try. I did a quick test and it seems to have worked just fine with the merged changes.

@alexcpsec
Copy link
Member

Cool! Thanks. I'll take it for a spin. Guess I need to stand up a CRITs instance 😀

@@ -22,14 +22,14 @@
parser.add_argument('--tiq-test', help="Output in tiq-test format", action="store_true")
args = parser.parse_args()

possible_types = ['csv', 'CSV']
possible_types = ['csv', 'json','crits']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no JSON support yet, so having 'json' here is misleading. :)

@alexcpsec
Copy link
Member

Conceptually and architecturally I am ok with this. I am not sure if @technoskald wants to do actual testing with a CRITs instance, but this would be otherwise good to go.

Paul, if you are interested, you could write a blog post that we can publish on https://mlsecproject.org/blog about this integration you developed. It could be helpful for others also, so let's put the word out there!

@paulpc
Copy link
Contributor Author

paulpc commented Oct 25, 2014

I'd love to write up a bit about the integration. How would i go about
doing that?
On Fri Oct 24 2014 at 5:21:07 PM Alex Pinto notifications@github.com
wrote:

Conceptually and architecturally I am ok with this. I am not sure if
@technoskald https://github.com/technoskald wants to do actual testing
with a CRITs instance, but this would be otherwise good to go.

Paul, if you are interested, you could write a blog post that we can
publish on https://mlsecproject.org/blog about this integration you
developed. It could be helpful for others also, so let's put the word out
there!


Reply to this email directly or view it on GitHub
#88 (comment).

@alexcpsec
Copy link
Member

I'll send you an e-mail about it. Thanks!

alexcpsec added a commit that referenced this pull request Nov 18, 2014
Multi-threaded code to upload the indicators into CRITs
@alexcpsec alexcpsec merged commit b57f95b into mlsecproject:master Nov 18, 2014
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

Successfully merging this pull request may close these issues.

2 participants