threatinator 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7b2a7120fd041938fb215c5ebc85d1e2d3d8bc71
+  data.tar.gz: a6cf7ee4eb833da92c650001aacce17dd2a1b4b4
+SHA512:
+  metadata.gz: 1557a2c0b6d59f2f1c03eeeccaef420ab1b920cdd4438d20e54c7be17530a6ee04d9ffc82b714780c9112b81a84812383922a25e05f8f72aa33b6bda39e10865
+  data.tar.gz: b153a90cfcafdfb2e3df1ba9d11b7bbb15ec255e43b96e0712268e063e631bd73e82a50e550c9f4560aa7282fc6b912f56eaa8eb9bc632ded8b0bf76cfbf2da1

data/CHANGELOG.md

@@ -0,0 +1,23 @@
+Next
+====
+
+* Your contribution here.
+
+0.1.1
+====
+
+* Remember to rev the changelog. [@justfalter](https://github.com/justfalter)
+
+0.1.0
+====
+
+* [#56](https://github.com/cikl/threatinator/pull/56): Gemify threatinator - [@justfalter](https://github.com/justfalter)
+* [#55](https://github.com/cikl/threatinator/pull/55): Rewrote configuration handling - [@justfalter](https://github.com/justfalter)
+* [#51](https://github.com/cikl/threatinator/pull/51): Clean up spec layout - [@justfalter](https://github.com/justfalter)
+* [#43](https://github.com/cikl/threatinator/issues/43): Make output modules pluggable - [@justfalter](https://github.com/justfalter)
+* [#46](https://github.com/cikl/threatinator/pull/46): Relocate all parsers related stuff to parser directory - [@justfalter](https://github.com/justfalter)
+* [#40](https://github.com/cikl/threatinator/pull/40): Add feed handler for Phishtank - [@justfalter](https://github.com/justfalter)
+* [#40](https://github.com/cikl/threatinator/pull/40): Break support for JRuby until we find a decent JSON parser - [@justfalter](https://github.com/justfalter)
+* [#40](https://github.com/cikl/threatinator/pull/40): Add JSON parsing support - [@justfalter](https://github.com/justfalter)
+* [#33](https://github.com/cikl/threatinator/pull/33): Add CSV parsing support - [@justfalter](https://github.com/justfalter)
+

data/CONTRIBUTING.md

@@ -0,0 +1,119 @@
+Contributing to Threatinator
+============================
+
+You're encouraged to submit [pull requests](https://github.com/cikl/threatinator/pulls), [propose features and discuss issues](https://github.com/cikl/threatinator/issues).
+
+#### Fork the Project
+
+Fork the [project on Github](https://github.com/cikl/threatinator) and check out your copy.
+
+```
+git clone https://github.com/contributor/threatinator.git
+cd threatinator
+git remote add upstream https://github.com/cikl/threatinator.git
+```
+
+#### Create a Topic Branch
+
+All active development is based off of our 'develop' branch. So, make sure your references are up to date, and create your topic branch off of upstream/develop.
+
+```
+git fetch upstream
+git checkout -b my-feature-branch upstream/develop
+```
+
+#### Write Tests
+
+If the area of code that you're working on supports unit tests, add tests. 
+Also, be sure to run all tests to make sure you didn't break anything.
+
+#### Write Code
+
+Implement your feature or bug fix.
+
+#### Write Documentation
+
+Document any external behavior in the [README](README.md).
+
+#### Update Changelog
+
+Add a line to [CHANGELOG](CHANGELOG.md) under *Next Release*. Make it look like every other line, including your name and link to your Github account.
+
+#### Commit Changes
+
+Make sure git knows your name and email address:
+
+```
+git config --global user.name "Your Name"
+git config --global user.email "contributor@example.com"
+```
+
+Make commits of logical units. This might mean making multiple commits if you're changing distinct bits of functionality. 
+```
+git add ...
+git commit
+```
+
+It's very important that you write a good commit log! It should describe what changed and why. If you're fixing an issue that is already tracked within Github, mention it!
+
+````
+    Make a commit title that is brief and to the point
+
+    - Describe the change you made, and why you made it.
+    - Context is vital to a good commit message. Try to get future developers
+      up to speed with what your change does so that they don't bother you
+      offline. 
+    - Mention any relevant Threatinator issues by mentioning the number like this #55 
+    - Github will automatically close any issues when your pull request is
+      accepted if you do something like this: closes #123
+
+````
+
+#### Rebase
+
+It's easy to for your feature branch to fall behind any changes that have been made in the main repository. This is to be expected on actively developed projects.
+In order to make sure that your changes will still work when merged into the main repo, it's a good idea to rebase your feature branch. This basically peels the commits off of your feature branch, pulls in any updates that have been made to upstream/develop, and then re-applies your commits. If all goes well, your commits will apply cleanly. If, however, someone else has made changes to the same code as you, git will report the conflicts and give you a chance to fix anything. 
+
+Basically, this will help ensure that your code will merge properly with any changes that may have been made in the main repository. If there are any conflicts, it will be easier to deal with those now, rather than finding out that your pull request can't merge.
+
+```
+git fetch upstream
+git rebase upstream/develop
+```
+
+#### Push
+
+```
+git push origin my-feature-branch
+```
+
+#### Make a Pull Request
+
+Go to https://github.com/contributor/threatinator and select your feature branch. Click the 'Pull Request' button and fill out the form. Pull requests are usually reviewed within a few days.
+
+#### Update CHANGELOG Again
+
+Update the [CHANGELOG](CHANGELOG.md) with the pull request number. A typical entry looks as follows.
+
+```
+* [#123](https://github.com/cikl/threatinator/pull/123): Reticulated splines - [@contributor](https://github.com/contributor).
+```
+
+Amend your previous commit and force push the changes.
+
+```
+git commit --amend
+git push origin my-feature-branch -f
+```
+
+#### Check on Your Pull Request
+
+Go back to your pull request after a few minutes and see whether it passed muster with Travis-CI. Everything should look green, otherwise fix issues and amend your commit as described above.
+
+#### Be Patient
+
+It's likely that your change will not be merged and that the nitpicky maintainers will ask you to do more, or fix seemingly benign problems. Hang on there!
+
+#### Thank You
+
+Please do know that we really appreciate and value your time and work. We love you, really.

data/Gemfile

@@ -0,0 +1,28 @@
+# A sample Gemfile
+source "https://rubygems.org"
+
+gem 'typhoeus', '~> 0.6'
+gem 'nokogiri', '~> 1.6'
+gem 'docile', '~> 1.1'
+gem 'virtus', '~> 1.0'
+gem 'gli', '~> 2.12'
+
+platforms :mingw, :mswin, :ruby do
+  gem 'oj', '~> 2.9'
+end
+
+group :test do
+  gem 'rake'
+  gem 'multi_json', '~> 1.10'
+  gem 'simplecov', '~> 0.9'
+  gem 'simplecov-vim', '= 0.0.1'
+  gem 'rspec', '~> 3'
+  gem 'rspec-its', '~> 1'
+  gem 'webmock', '~> 1'
+  gem 'factory_girl', '~> 4'
+end
+
+group :development do
+  gem 'jeweler', '~> 2'
+  gem 'pry', '~> 0.10'
+end

data/LICENSE

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/README.md

@@ -0,0 +1,45 @@
+# Threatinator
+Threatinator is a ruby library for parsing threat data feeds. It is a component of [Cikl](https://github.com/cikl/cikl), a threat intelligence management system. 
+## Source code repository
+
+The repository is located at: https://github.com/cikl/threatinator
+
+## Development
+
+First, set up your dependencies.
+
+```
+bundle install
+```
+
+### Listing feeds
+
+```
+bundle exec bin/threatinator list
+```
+
+### Running a feed
+
+```
+bundle exec bin/threatinator run alienvault ip_reputation
+```
+
+### Getting help
+
+All commands respond to '--help' to provide details on their usage. 
+
+```
+bundle exec bin/threatinator run --help
+```
+
+## Contributing and Issue Tracking
+
+Before you file a bug or submit a pull request, please review our 
+[contribution guidelines](https://github.com/cikl/cikl/wiki/Contributing).
+
+All issues are managed here: [cikl/threatinator/issues](https://github.com/cikl/threatinator/issues).
+
+## License
+Copyright (C) 2014 Michael Ryan (github.com/justfalter)
+
+See the LICENSE file for license rights and limitations (LGPLv3).

data/Rakefile

@@ -0,0 +1,45 @@
+require 'rubygems'
+require 'bundler'
+begin
+  Bundler.setup(:default, :development, :test)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
+require 'rake'
+
+begin
+  require 'jeweler'
+rescue LoadError
+else 
+  Jeweler::Tasks.new do |gem|
+    # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
+    gem.name = "threatinator"
+    gem.homepage = "http://github.com/cikl/threatinator"
+    gem.license = "LGLv3"
+    gem.summary = %Q{Threatinator is a library and tool for parsing threat data feeds.}
+    gem.description = gem.summary
+    gem.email = "falter@gmail.com"
+    gem.authors = ["Mike Ryan", "Pierre Lamy"]
+    gem.files  = 
+      ['bin/threatinator'] + 
+      Dir.glob("lib/**/*.rb") + 
+      Dir.glob("spec/**/*") + 
+      %w(CONTRIBUTING.md CHANGELOG.md LICENSE Gemfile README.md Rakefile VERSION)
+
+  end
+  Jeweler::RubygemsDotOrgTasks.new
+end
+
+begin
+  require 'rspec/core'
+  require 'rspec/core/rake_task'
+rescue LoadError
+else
+  RSpec::Core::RakeTask.new(:spec) do |spec|
+    spec.pattern = FileList['spec/**/*_spec.rb']
+  end
+end
+
+task :default => [ :spec ]

data/VERSION

@@ -0,0 +1 @@
+0.1.1

data/bin/threatinator

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+$:.unshift File.expand_path("../../lib", __FILE__)
+require 'threatinator/cli'
+ret = Threatinator::CLI.process!(ARGV)
+exit ret