otx_ruby 0.9.9 → 0.9.10

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
- SHA1:
3
- metadata.gz: 5a1f58f203045e22c67f839a83ba904693b24b78
4
- data.tar.gz: e9b947e95e17e7d72efc67da5b19744843c08722
2
+ SHA256:
3
+ metadata.gz: a3baba539784a8d0b9bfbb8bfe953fb746bb34169615c3b4916c83cbdfdce51d
4
+ data.tar.gz: 2dd5a31f5f2830e332d0d2e312f30d785cf49d738135d82b391ba23d25e2e02d
5
5
  SHA512:
6
- metadata.gz: e26bc7b16a7f836a797f645a8334ca8dddff0d1c0c05c62646dcd52e8f1ea3273b9c417c245011782d0d8bbb83fc721fb585c224713e3377965de9f1e9eeaa75
7
- data.tar.gz: 0bbf5ac93d40cdf87df93a016805d052e431b7818c7034bb5aa3e10c001bb93e852e6062b2b20217b027c1d3bb04354a18c1676a6733fad707d69cb15ffb6931
6
+ metadata.gz: 3a632013e5e9246964f229efbcd42ce73a5b8e773049b68392bc2edcaf3b2188bb3acf3917855e744dae98e260f08f3153f2d5a5028636b94864ca28745a8580
7
+ data.tar.gz: ab01e990b2d3401cb98101ece7f52fb3015918ba0ded60065d5bb4088f7a457ff0d02b3ab3ad4f751b2098758ccd4bb0bb927b80bcad20e57a1cca2b32f03a6b
@@ -0,0 +1,64 @@
1
+ version: 2
2
+ jobs:
3
+ build:
4
+ working_directory: ~/reapertech/otx_ruby
5
+ parallelism: 1
6
+ shell: /bin/bash --login
7
+ environment:
8
+ CIRCLE_ARTIFACTS: /tmp/circleci-artifacts
9
+ CIRCLE_TEST_REPORTS: /tmp/circleci-test-results
10
+ docker:
11
+ - image: cimg/ruby:3.0.4-browsers
12
+ steps:
13
+ - checkout
14
+ - run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS
15
+ - run: sudo apt-get update
16
+ - run: sudo apt-get install cmake
17
+ - run: sudo gem install bundler-audit
18
+ - run:
19
+ command: sudo gem install brakeman
20
+ - restore_cache:
21
+ keys:
22
+ - v1-dep-{{ .Branch }}-
23
+ - v1-dep-master-
24
+ - v1-dep-
25
+ - run: gem install bundler --version 2.3.17
26
+ - run: echo -e "export RAILS_ENV=test\nexport RACK_ENV=test" >> $BASH_ENV
27
+ - run:
28
+ "bundle check --path=vendor/bundle || bundle install --path=vendor/bundle
29
+ --jobs=4 --retry=3 "
30
+ - save_cache:
31
+ key: v1-dep-{{ .Branch }}-{{ epoch }}
32
+ paths:
33
+ - vendor/bundle
34
+ - ~/virtualenvs
35
+ - ~/.m2
36
+ - ~/.ivy2
37
+ - ~/.bundle
38
+ - ~/.go_workspace
39
+ - ~/.gradle
40
+ - ~/.cache/bower
41
+ - run: echo 'no database'
42
+ - run:
43
+ command: bundle exec rake test
44
+ environment:
45
+ RAILS_ENV: test
46
+ RACK_ENV: test
47
+ - run:
48
+ name: Run Bundle Audit
49
+ command: |
50
+ sudo gem install bundler-audit
51
+ bundle audit update && bundle audit check
52
+ - run:
53
+ name: Build and publish gem
54
+ command: |
55
+ gem build otx_ruby.gemspec
56
+ cp otx_ruby-*.gem $CIRCLE_ARTIFACTS
57
+ gem push $CIRCLE_ARTIFACTS/otx_ruby-*.gem; true
58
+ - store_test_results:
59
+ path: /tmp/circleci-test-results
60
+ # Save artifacts
61
+ - store_artifacts:
62
+ path: /tmp/circleci-artifacts
63
+ - store_artifacts:
64
+ path: /tmp/circleci-test-results
data/.gitignore CHANGED
@@ -1,3 +1,80 @@
1
+ # File created using '.gitignore Generator' for Visual Studio Code: https://bit.ly/vscode-gig
2
+
3
+ # Created by https://www.toptal.com/developers/gitignore/api/visualstudiocode,linux,go,macos
4
+ # Edit at https://www.toptal.com/developers/gitignore?templates=visualstudiocode,linux,go,macos
5
+
6
+ ### Linux ###
7
+ *~
8
+
9
+ # temporary files which can be created if a process still has a handle open of a deleted file
10
+ .fuse_hidden*
11
+
12
+ # KDE directory preferences
13
+ .directory
14
+
15
+ # Linux trash folder which might appear on any partition or disk
16
+ .Trash-*
17
+
18
+ # .nfs files are created when an open file is removed but is still being accessed
19
+ .nfs*
20
+
21
+ ### macOS ###
22
+ # General
23
+ .DS_Store
24
+ .AppleDouble
25
+ .LSOverride
26
+
27
+ # Icon must end with two \r
28
+ Icon
29
+
30
+ # Thumbnails
31
+ ._*
32
+
33
+ # Files that might appear in the root of a volume
34
+ .DocumentRevisions-V100
35
+ .fseventsd
36
+ .Spotlight-V100
37
+ .TemporaryItems
38
+ .Trashes
39
+ .VolumeIcon.icns
40
+ .com.apple.timemachine.donotpresent
41
+
42
+ # Directories potentially created on remote AFP share
43
+ .AppleDB
44
+ .AppleDesktop
45
+ Network Trash Folder
46
+ Temporary Items
47
+ .apdisk
48
+
49
+ ### macOS Patch ###
50
+ # iCloud generated files
51
+ *.icloud
52
+
53
+ ### VisualStudioCode ###
54
+ .vscode/*
55
+ !.vscode/settings.json
56
+ !.vscode/tasks.json
57
+ !.vscode/launch.json
58
+ !.vscode/extensions.json
59
+ !.vscode/*.code-snippets
60
+
61
+ # Local History for Visual Studio Code
62
+ .history/
63
+
64
+ # Built Visual Studio Code Extensions
65
+ *.vsix
66
+
67
+ ### VisualStudioCode Patch ###
68
+ # Ignore all local history of files
69
+ .history
70
+ .ionide
71
+
72
+ # Support for Project snippet scope
73
+
74
+ # End of https://www.toptal.com/developers/gitignore/api/visualstudiocode,linux,go,macos
75
+
76
+ # Custom rules (everything added below won't be overriden by 'Generate .gitignore File' if you use 'Update' option)
77
+
1
78
  /.bundle/
2
79
  /.yardoc
3
80
  /Gemfile.lock
@@ -7,3 +84,5 @@
7
84
  /pkg/
8
85
  /spec/reports/
9
86
  /tmp/
87
+ /.tool-versions
88
+ tags
data/LICENSE.md CHANGED
@@ -1,4 +1,4 @@
1
- Copyright (c) 2015-2016 Stephen Kapp
1
+ Copyright (c) 2015-2022 Stephen Kapp and Reaper Technologies Limited
2
2
 
3
3
  Licensed under the Apache License, Version 2.0 (the "License");
4
4
  you may not use this file except in compliance with the License.
data/README.md CHANGED
@@ -7,6 +7,7 @@ This gem provides a wrapper for Ruby applications to pull pulses from OTX and be
7
7
  ## Build Status
8
8
 
9
9
  [![security](https://hakiri.io/github/mort666/otx_ruby/master.svg)](https://hakiri.io/github/mort666/otx_ruby/master) [![CircleCI](https://circleci.com/gh/mort666/otx_ruby/tree/master.svg?style=svg)](https://circleci.com/gh/mort666/otx_ruby/tree/master)
10
+
10
11
  ## Installation
11
12
 
12
13
  Add this line to your application's Gemfile:
@@ -65,4 +66,4 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/mort66
65
66
 
66
67
  ## Copyright
67
68
 
68
- Copyright (c) 2015-2016 Stephen Kapp. See LICENSE for details.
69
+ Copyright (c) 2015-2022 Stephen Kapp and Reaper Technologies Limited. See LICENSE for details.
data/SECURITY.md ADDED
@@ -0,0 +1,80 @@
1
+ # Vulnerability Reporting and Security Policy
2
+
3
+ ## Introduction
4
+
5
+ Reaper Technologies welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.
6
+
7
+ ## Supported Releases
8
+
9
+ Reaper Technologies code is typically deployed in a SaaS manner, as such support is limited to the release currently in our production environments, for those deployments.
10
+
11
+ For code that access is provided by other means and is available for use as a dependency or similar, we follow the following support model.
12
+
13
+ We will normally use Semantic Versioning (https://semver.org/) for release labelling, as a result when considering support we support the current MAJOR.MINOR release irrespective of PATCH as first priority.
14
+
15
+ We support the current MAJOR.MINOR minus one MINOR release irrespective of PATCH. For example if a current release is 1.10.111 then we will support releases 1.9.100 and 1.9.90. However, we will not support 1.8.60 directly unless an issue affects the 1.9.100/1.9.90 and/or 1.10.111 releases.
16
+
17
+ ## Systems, Services and Software in Scope
18
+
19
+ This policy applies to any digital assets owned, operated, or maintained by Reaper Technologies.
20
+
21
+ ## Out of Scope
22
+
23
+ - Assets or other equipment not owned by parties participating in this policy.
24
+
25
+ Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
26
+
27
+ ## Reporting a Vulnerability (Official Channels)
28
+
29
+ For vulnerability reporting and disclosure, we operate under Coordinated Vulnerability Disclosure (CVD) principles as detailed in:
30
+
31
+ - [ISO/IEC 29147:2018 on Vulnerability Disclosure](https://www.iso.org/standard/72311.html)
32
+ - [The CERT Guide to Coordinated Vulnerability Disclosure](https://resources.sei.cmu.edu/asset_files/SpecialReport/2017_003_001_503340.pdf)
33
+
34
+ Where possible vulnerabilities should be reported to secops@reapertech.com in the first instance for any Reaper Technologies product or service. As we are a small team, please allow 14 days for an initial response to a mail to the SecOps mail box. We will normally in the response outline our expected next steps and our assessment of any issue.
35
+
36
+ For publicly available code posted to GitHub, vulnerabilities should also be reported to the project issue tracker and be tagged as 'SECURITY' with a issue label as well as in the Issue title along side a mail to the SecOps mailbox. Likewise we will endeavour to provide an initial response within 14 days.
37
+
38
+ When reporting any issue please provide as much detail as possible in the report to enable us to identify an issue, replicate the issue and suggestions for ways to address any issue are welcomed.
39
+
40
+ For our open source releases if a report is provided with a PR for a fix, we will generally review and merge any fix and update the repository and any associated release as applicable.
41
+
42
+ Other channels may be made available on a individual service or product basis such as through a Bug Bounty Scheme, requirements for those will be published alongside the product or service.
43
+
44
+ ## Our Commitments
45
+
46
+ When working with us, according to this policy, you can expect us to:
47
+
48
+ - Respond to your report promptly (please allow us 14 days), and work with you to understand and validate your report;
49
+ - Strive to keep you informed about the progress of a vulnerability as it is processed;
50
+ - Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
51
+ - Extend Safe Harbour for your vulnerability research that is related to this policy.
52
+
53
+ ## Our Expectations
54
+
55
+ In participating in our vulnerability disclosure program in good faith, we ask that you:
56
+
57
+ - Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
58
+ - Report any vulnerability you’ve discovered promptly;
59
+ - Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
60
+ - Use only the Official Channels to discuss vulnerability information with us;
61
+ - Provide us a reasonable amount of time (at least 120 days from the initial report) to resolve the issue before you disclose it publicly;
62
+ - Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
63
+ - If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
64
+ - You should only interact with test accounts you own or with explicit permission from the account holder; and
65
+ - Do not engage in extortion.
66
+
67
+ ## Safe Harbour
68
+
69
+ When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:
70
+
71
+ - Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
72
+ - Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
73
+ - Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
74
+ - Lawful, helpful to the overall security of the Internet, and conducted in good faith.
75
+
76
+ You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
77
+
78
+ If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
79
+
80
+ > Note that the Safe Harbour applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.
@@ -1,4 +1,4 @@
1
1
  module OTX
2
2
  # Library Version Number
3
- VERSION = "0.9.9"
3
+ VERSION = "0.9.10"
4
4
  end
data/otx_ruby.gemspec CHANGED
@@ -10,20 +10,21 @@ Gem::Specification.new do |spec|
10
10
  spec.email = ["mort666@virus.org"]
11
11
  spec.summary = %q{AlienVault OTX Ruby Gem}
12
12
  spec.description = %q{AlienVault Open Threat Exchange Threat Intel feed API Wrapper}
13
- spec.homepage = "http://github.com/mort666/otx_ruby"
13
+ spec.homepage = "https://github.com/mort666/otx_ruby"
14
14
  spec.license = "Apache-2.0"
15
+ spec.required_ruby_version = Gem::Requirement.new(">= 3.0.0")
15
16
 
16
17
  spec.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
17
18
  spec.bindir = "exe"
18
19
  spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
19
20
  spec.require_paths = ["lib"]
20
21
 
21
- spec.add_dependency "faraday", "~> 0.11"
22
- spec.add_dependency "oj", "~> 3.6.5"
22
+ spec.add_dependency "faraday", "~> 2.3"
23
+ spec.add_dependency "oj", "~> 3.13"
23
24
 
24
- spec.add_development_dependency "bundler", "~> 1.15"
25
- spec.add_development_dependency "rake", "~> 12.3"
26
- spec.add_development_dependency "minitest", "~> 5.11"
27
- spec.add_development_dependency "vcr", "~> 4.0"
28
- spec.add_development_dependency "webmock", "~> 3.4.2"
25
+ spec.add_development_dependency "bundler", "~> 2.3"
26
+ spec.add_development_dependency "rake", "~> 13.0"
27
+ spec.add_development_dependency "minitest", "~> 5.16"
28
+ spec.add_development_dependency "vcr", "~> 6.1"
29
+ spec.add_development_dependency "webmock", "~> 3.14"
29
30
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: otx_ruby
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.9
4
+ version: 0.9.10
5
5
  platform: ruby
6
6
  authors:
7
7
  - Stephen Kapp
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2018-08-02 00:00:00.000000000 Z
11
+ date: 2022-07-12 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: faraday
@@ -16,98 +16,98 @@ dependencies:
16
16
  requirements:
17
17
  - - "~>"
18
18
  - !ruby/object:Gem::Version
19
- version: '0.11'
19
+ version: '2.3'
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - "~>"
25
25
  - !ruby/object:Gem::Version
26
- version: '0.11'
26
+ version: '2.3'
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: oj
29
29
  requirement: !ruby/object:Gem::Requirement
30
30
  requirements:
31
31
  - - "~>"
32
32
  - !ruby/object:Gem::Version
33
- version: 3.6.5
33
+ version: '3.13'
34
34
  type: :runtime
35
35
  prerelease: false
36
36
  version_requirements: !ruby/object:Gem::Requirement
37
37
  requirements:
38
38
  - - "~>"
39
39
  - !ruby/object:Gem::Version
40
- version: 3.6.5
40
+ version: '3.13'
41
41
  - !ruby/object:Gem::Dependency
42
42
  name: bundler
43
43
  requirement: !ruby/object:Gem::Requirement
44
44
  requirements:
45
45
  - - "~>"
46
46
  - !ruby/object:Gem::Version
47
- version: '1.15'
47
+ version: '2.3'
48
48
  type: :development
49
49
  prerelease: false
50
50
  version_requirements: !ruby/object:Gem::Requirement
51
51
  requirements:
52
52
  - - "~>"
53
53
  - !ruby/object:Gem::Version
54
- version: '1.15'
54
+ version: '2.3'
55
55
  - !ruby/object:Gem::Dependency
56
56
  name: rake
57
57
  requirement: !ruby/object:Gem::Requirement
58
58
  requirements:
59
59
  - - "~>"
60
60
  - !ruby/object:Gem::Version
61
- version: '12.3'
61
+ version: '13.0'
62
62
  type: :development
63
63
  prerelease: false
64
64
  version_requirements: !ruby/object:Gem::Requirement
65
65
  requirements:
66
66
  - - "~>"
67
67
  - !ruby/object:Gem::Version
68
- version: '12.3'
68
+ version: '13.0'
69
69
  - !ruby/object:Gem::Dependency
70
70
  name: minitest
71
71
  requirement: !ruby/object:Gem::Requirement
72
72
  requirements:
73
73
  - - "~>"
74
74
  - !ruby/object:Gem::Version
75
- version: '5.11'
75
+ version: '5.16'
76
76
  type: :development
77
77
  prerelease: false
78
78
  version_requirements: !ruby/object:Gem::Requirement
79
79
  requirements:
80
80
  - - "~>"
81
81
  - !ruby/object:Gem::Version
82
- version: '5.11'
82
+ version: '5.16'
83
83
  - !ruby/object:Gem::Dependency
84
84
  name: vcr
85
85
  requirement: !ruby/object:Gem::Requirement
86
86
  requirements:
87
87
  - - "~>"
88
88
  - !ruby/object:Gem::Version
89
- version: '4.0'
89
+ version: '6.1'
90
90
  type: :development
91
91
  prerelease: false
92
92
  version_requirements: !ruby/object:Gem::Requirement
93
93
  requirements:
94
94
  - - "~>"
95
95
  - !ruby/object:Gem::Version
96
- version: '4.0'
96
+ version: '6.1'
97
97
  - !ruby/object:Gem::Dependency
98
98
  name: webmock
99
99
  requirement: !ruby/object:Gem::Requirement
100
100
  requirements:
101
101
  - - "~>"
102
102
  - !ruby/object:Gem::Version
103
- version: 3.4.2
103
+ version: '3.14'
104
104
  type: :development
105
105
  prerelease: false
106
106
  version_requirements: !ruby/object:Gem::Requirement
107
107
  requirements:
108
108
  - - "~>"
109
109
  - !ruby/object:Gem::Version
110
- version: 3.4.2
110
+ version: '3.14'
111
111
  description: AlienVault Open Threat Exchange Threat Intel feed API Wrapper
112
112
  email:
113
113
  - mort666@virus.org
@@ -116,14 +116,15 @@ extensions: []
116
116
  extra_rdoc_files: []
117
117
  files:
118
118
  - ".byebug_history"
119
+ - ".circleci/config.yml"
119
120
  - ".gitignore"
120
121
  - Gemfile
121
122
  - LICENSE.md
122
123
  - README.md
123
124
  - Rakefile
125
+ - SECURITY.md
124
126
  - bin/console
125
127
  - bin/setup
126
- - circle.yml
127
128
  - lib/otx_ruby.rb
128
129
  - lib/otx_ruby/activity.rb
129
130
  - lib/otx_ruby/base.rb
@@ -168,7 +169,7 @@ files:
168
169
  - lib/otx_ruby/users.rb
169
170
  - lib/otx_ruby/version.rb
170
171
  - otx_ruby.gemspec
171
- homepage: http://github.com/mort666/otx_ruby
172
+ homepage: https://github.com/mort666/otx_ruby
172
173
  licenses:
173
174
  - Apache-2.0
174
175
  metadata: {}
@@ -180,15 +181,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
180
181
  requirements:
181
182
  - - ">="
182
183
  - !ruby/object:Gem::Version
183
- version: '0'
184
+ version: 3.0.0
184
185
  required_rubygems_version: !ruby/object:Gem::Requirement
185
186
  requirements:
186
187
  - - ">="
187
188
  - !ruby/object:Gem::Version
188
189
  version: '0'
189
190
  requirements: []
190
- rubyforge_project:
191
- rubygems_version: 2.6.14
191
+ rubygems_version: 3.3.11
192
192
  signing_key:
193
193
  specification_version: 4
194
194
  summary: AlienVault OTX Ruby Gem
data/circle.yml DELETED
@@ -1,9 +0,0 @@
1
- machine:
2
- ruby:
3
- version: 2.3.5
4
- database:
5
- override:
6
- - echo 'no database'
7
- dependencies:
8
- pre:
9
- - gem install bundler