script_core 0.2.3 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c19d1c83197db63d2ddbf7f70ed6f02fd5398d6f1247d84b0f21b7152bc69d5d
-  data.tar.gz: ce5ef153d196492d536a18bd04a39b0e7137fa2411e0c9dc55ad0a38a7a87e1f
+  metadata.gz: d4acca39fe051a66bcfc3333033a4560384d47d4bfec2f720727e6ea3a1d95d7
+  data.tar.gz: a292055ceab794414997aa2499b534982128b7a162460129b7a40dfea9ebe020
 SHA512:
-  metadata.gz: 68cb35a85e86480436c3c8a2dfa8ae8ded6f8f31c93e4429d37dd63dea54503b1d902383743327a2d967f4735ad39613cbf3eb319d72c25ce7e2dd93649b819a
-  data.tar.gz: 804c806c5328bb8785e1011f28bf4655bd607c083646f11d8e78a66caad3abd45d92af74beb2ca752a3019f3e949e1412e6325bf023a7f9d5f67f340aa33e315
+  metadata.gz: 641afdbc91371e1c094df80b281b3986885dd8304050e4360c4c3663567ddddd685af88bbe1e33b88c28056f2475844887c6af159a6af1ad5dd8156c6f3481c9
+  data.tar.gz: 6727cb3110d66635586beb109f34181481eaef4b7827c238b09bb9e006b970413aa89d6997c26d4e3c4e42e195f96ee073553ebfb31c8561480aa87938b63e38

data/.rubocop.yml

@@ -4,6 +4,7 @@ require:
 
 AllCops:
   TargetRubyVersion: 2.5
+  DisabledByDefault: true
   Exclude:
     - bin/**/*
     - tests/**/*
@@ -15,35 +16,8 @@ AllCops:
     - spec/dummy/db/schema.rb
     - spec/dummy/bin/**/*
 
-Rails:
-  Enabled: true
-
-Layout/LineLength:
-  Max: 150
-
-Metrics/MethodLength:
-  Max: 100
-
-Metrics/BlockLength:
-  Max: 50
-
-Metrics/ClassLength:
-  Enabled: false
-
-Style/GuardClause:
-  Enabled: false
-
-Style/Documentation:
-  Enabled: false
-
-Style/ClassAndModuleChildren:
-  Enabled: false
-
-Naming/AccessorMethodName:
-  Enabled: false
-
-Naming/MemoizedInstanceVariableName:
-  Enabled: false
+#Metrics/AbcSize:
+#  Max: 30
 
 # Prefer assert_not over assert !
 Rails/AssertNot:
@@ -55,25 +29,23 @@ Rails/RefuteMethods:
   Include:
     - 'test/**/*'
 
-# Prefer &&/|| over and/or.
-Style/AndOr:
+Rails/IndexBy:
   Enabled: true
 
-# Do not use braces for hash literals when they are the last argument of a
-# method call.
-Style/HashEachMethods:
+Rails/IndexWith:
   Enabled: true
 
-Style/HashTransformKeys:
-  Enabled: true
-
-Style/HashTransformValues:
+# Prefer &&/|| over and/or.
+Style/AndOr:
   Enabled: true
 
 # Align `when` with `case`.
 Layout/CaseIndentation:
   Enabled: true
 
+Layout/ClosingHeredocIndentation:
+  Enabled: true
+
 # Align comments with method definitions.
 Layout/CommentIndentation:
   Enabled: true
@@ -91,6 +63,9 @@ Layout/EndAlignment:
 Layout/EmptyLineAfterMagicComment:
   Enabled: true
 
+Layout/EmptyLinesAroundAccessModifier:
+  Enabled: true
+
 Layout/EmptyLinesAroundBlockBody:
   Enabled: true
 
@@ -106,13 +81,13 @@ Layout/EmptyLinesAroundMethodBody:
 Layout/EmptyLinesAroundModuleBody:
   Enabled: true
 
-Layout/FirstArgumentIndentation:
-  Enabled: true
-
 # Use Ruby >= 1.9 syntax for hashes. Prefer { a: :b } over { :a => :b }.
 Style/HashSyntax:
   Enabled: true
 
+Layout/FirstArgumentIndentation:
+  Enabled: true
+
 # Method definitions after `private` or `protected` isolated calls need one
 # extra level of indentation.
 Layout/IndentationConsistency:
@@ -141,10 +116,10 @@ Layout/SpaceAroundEqualsInParameterDefault:
 Layout/SpaceAroundKeyword:
   Enabled: true
 
-Layout/SpaceAroundOperators:
+Layout/SpaceBeforeComma:
   Enabled: true
 
-Layout/SpaceBeforeComma:
+Layout/SpaceBeforeComment:
   Enabled: true
 
 Layout/SpaceBeforeFirstArg:
@@ -164,9 +139,6 @@ Style/FrozenStringLiteralComment:
 Style/RedundantFreeze:
   Enabled: true
 
-Style/AccessModifierDeclarations:
-  Enabled: false
-
 # Use `foo {}` not `foo{}`.
 Layout/SpaceBeforeBlockBraces:
   Enabled: true
@@ -192,7 +164,7 @@ Style/StringLiterals:
 Layout/IndentationStyle:
   Enabled: true
 
-# Blank lines should not have any spaces.
+# Empty lines should not have any spaces.
 Layout/TrailingEmptyLines:
   Enabled: true
 
@@ -200,9 +172,6 @@ Layout/TrailingEmptyLines:
 Layout/TrailingWhitespace:
   Enabled: true
 
-Layout/SpaceAroundMethodCallOperator:
-  Enabled: true
-
 # Use quotes for string literals when they are enough.
 Style/RedundantPercentQ:
   Enabled: true
@@ -235,19 +204,16 @@ Lint/UselessAssignment:
 Lint/DeprecatedClassMethods:
   Enabled: true
 
-Lint/AssignmentInCondition:
-  Enabled: false
-
-Lint/RaiseException:
+Lint/DeprecatedOpenSSLConstant:
   Enabled: true
 
-Lint/StructNewOverride:
+Style/ParenthesesAroundCondition:
   Enabled: true
 
-Style/ExponentialNotation:
+Style/HashTransformKeys:
   Enabled: true
 
-Style/ParenthesesAroundCondition:
+Style/HashTransformValues:
   Enabled: true
 
 Style/RedundantBegin:
@@ -268,6 +234,12 @@ Style/ColonMethodCall:
 Style/TrivialAccessors:
   Enabled: true
 
+Style/SlicingWithRange:
+  Enabled: true
+
+Style/RedundantRegexpEscape:
+  Enabled: true
+
 Performance/FlatMap:
   Enabled: true
 
@@ -288,3 +260,9 @@ Performance/ReverseEach:
 
 Performance/UnfreezeString:
   Enabled: true
+
+Performance/DeletePrefix:
+  Enabled: true
+
+Performance/DeleteSuffix:
+  Enabled: true

data/.ruby-version

@@ -1 +1 @@
-2.7.1
+3.0.0

data/Gemfile

@@ -12,14 +12,14 @@ gem "sqlite3"
 # Use Puma as the app server
 gem "puma"
 
-gem "listen", ">= 3.0.5", "< 3.2"
+gem "listen", "~> 3.1"
 # Access an IRB console on exception pages or by using <%= console %> anywhere in the code.
 gem "web-console", group: :development
 # Call "byebug" anywhere in the code to stop execution and get a debugger console
 gem "byebug", group: %i[development test]
 
 # To support ES6
-gem "sprockets", "~> 4.0.0"
+gem "sprockets", "~> 4.0"
 # Support ES6
 gem "babel-transpiler"
 # Use SCSS for stylesheets

data/README.md

@@ -23,13 +23,19 @@ I want to make these changes:
     - [ ] Find a good way to working with timezone on mruby side
     - [ ] Find a good way to working with `BigDecimal` & `Date` (mruby doesn't have these) on mruby side
 
-## Restrictions
+## limitation
 
 - We enable `MRB_DISABLE_STDIO` flag when compiling mruby,
   which means the sandbox will not support gems which dependent `mruby-io` or `stdio.h`,
   the result is you can not do any HTTP request, read and write files in the sandbox,
   you may consider preparing data on Ruby side and pass them to the sandbox.
 
+## Help wanted
+
+I'm not familiar with C/CPP, so I can't improve ESS (in `ext/enterprise_script_service`),
+
+Currently there're too much warnings on compiling, hope some one could help to resolve them.
+
 ## Demo
 
 Clone the repository.

data/ext/enterprise_script_service/Rakefile

@@ -41,7 +41,7 @@ Dir.chdir("#{ESS_ROOT}/tests") do
   SERVICE_TESTS_EXECUTABLE = SERVICE_EXECUTABLE_DIR.join("enterprise_script_service_tests").to_s
 end
 
-MRUBY_BIN_DIR = MRUBY_DIR.join("build/host/bin")
+MRUBY_BIN_DIR = MRUBY_DIR.join("build/host/mrbc/bin")
 MRBC_EXE = MRUBY_BIN_DIR.join("mrbc")
 
 MRUBY_LIB_DIR = MRUBY_DIR.join("build/sandbox/lib")

data/ext/enterprise_script_service/libseccomp/.travis.yml

@@ -1,23 +1,28 @@
 # Travis CI configuration for libseccomp
 
-# https://docs.travis-ci.com/user/trusty-ci-environment
+# https://docs.travis-ci.com/user/reference/bionic
 # https://wiki.ubuntu.com/Releases
 
-dist: xenial
-sudo: false
+dist: bionic
 
 notifications:
   email:
     on_success: always
     on_failure: always
 
+arch:
+  - amd64
+  - arm64
+  - ppc64le
+
+os:
+  - linux
+
 language: c
 compiler:
   - gcc
 
 language: python
-python:
-  - "nightly"
 
 addons:
   coverity_scan:
@@ -34,6 +39,7 @@ addons:
       - valgrind
       - clang
       - lcov
+      - gperf
 
 env:
   global:
@@ -46,7 +52,10 @@ before_install:
   # assume the distro has an old version of cython
   - pip install cython
   # see https://github.com/eddyxu/cpp-coveralls
-  - pip install cpp-coveralls
+  - |
+    if [ $TRAVIS_CPU_ARCH == "amd64" ]; then
+      pip install cpp-coveralls
+    fi
 
 # perform the build and fail immediately on error
 install:
@@ -59,13 +68,16 @@ script:
   - ./configure --enable-python
   - make check-build
   - LIBSECCOMP_TSTCFG_STRESSCNT=5 make check
-  - LIBSECCOMP_TSTCFG_TYPE=live make -C tests check
-  # ubuntu 14.04 (trusty) clang has problems with the cython generated code
-  - make clean && ./configure && scan-build --status-bugs make
+  - LIBSECCOMP_TSTCFG_TYPE=live LIBSECCOMP_TSTCFG_MODE_LIST=c make -C tests check
+  - |
+    if [ $TRAVIS_CPU_ARCH == "amd64" -o -x scan-build ]; then
+      make clean && ./configure && scan-build --status-bugs make
+    fi
 
 after_success:
   # limit the code coverage tests to the 'test-code-coverage' target
-  - make clean && ./configure --enable-code-coverage && make test-code-coverage
   # https://github.com/eddyxu/cpp-coveralls/blob/master/README.md
-  - coveralls --gcov-options '\-lp'
-    --exclude tests --exclude tools --exclude src/arch-syscall-check.c
+  - |
+    if [ $TRAVIS_CPU_ARCH == "amd64" ]; then
+      make clean && ./configure --enable-code-coverage && make test-code-coverage && coveralls --gcov-options '\-lp' --exclude tests --exclude tools --exclude src/arch-syscall-check.c
+    fi

data/ext/enterprise_script_service/libseccomp/CHANGELOG

@@ -2,6 +2,38 @@ libseccomp: Releases
 ===============================================================================
 https://github.com/seccomp/libseccomp
 
+* Version 2.5.0 - July 20, 2020
+- Add support for the seccomp user notifications, see the
+  seccomp_notify_alloc(3), seccomp_notify_receive(3), seccomp_notify_respond(3)
+  manpages for more information
+- Add support for new filter optimization approaches, including a balanced tree
+  optimization, see the SCMP_FLTATR_CTL_OPTIMIZE filter attribute for more
+  information
+- Add support for the 64-bit RISC-V architecture
+- Performance improvements when adding new rules to a filter thanks to the use
+  of internal shadow transactions and improved syscall lookup tables
+- Properly document the libseccomp API return values and include them in the
+  stable API promise
+- Improvements to the s390 and s390x multiplexed syscall handling
+- Multiple fixes and improvements to the libseccomp manpages
+- Moved from manually maintained syscall tables to an automatically generated
+  syscall table in CSV format
+- Update the syscall tables to Linux v5.8.0-rc5
+- Python bindings and build now default to Python 3.x
+- Improvements to the tests have boosted code coverage to over 93%
+- Enable Travis CI testing on the aarch64 and ppc64le architectures
+- Add code inspection via lgtm.com
+
+* Version 2.4.3 - March 4, 2020
+- Add list of authorized release signatures to README.md
+- Fix multiplexing issue with s390/s390x shm* syscalls
+- Remove the static flag from libseccomp tools compilation
+- Add define for __SNR_ppoll
+- Update our Travis CI configuration to use Ubuntu 18.04
+- Disable live python tests in Travis CI
+- Use default python, rather than nightly python, in TravisCI
+- Fix potential memory leak identified by clang in the scmp_bpf_sim tool
+
 * Version 2.4.2 - November 7, 2019
 - Update the syscall table for Linux v5.4-rc4
 - Stop defining __NR_x values for syscalls that don't exist.  Libseccomp

data/ext/enterprise_script_service/libseccomp/CONTRIBUTING.md

@@ -8,7 +8,7 @@ to the rules described here, but by following the instructions below you
 should have a much easier time getting your work merged with the upstream
 project.
 
-## Test Your Code
+## Test Your Code Using Existing Tests
 
 There are three possible tests you can run to verify your code.  The first
 test is used to check the formatting and coding style of your changes, you
@@ -38,7 +38,7 @@ command:
 
 ... if there are any faults or errors they will be displayed.
 
-## Make Sure Your Code is Tested
+## Add New Tests for New Functionality
 
 The libseccomp code includes a fairly extensive test suite and any submissions
 which add functionality, or significantly change the existing code, should
@@ -50,29 +50,6 @@ base, and can be enabled via the "--enable-code-coverage" configure flag and
 the "check-code-coverage" make target.  Additional details on generating code
 coverage information can be found in the .travis.yml file.
 
-## Generate the Patch(es)
-
-Depending on how you decided to work with the libseccomp code base and what
-tools you are using there are different ways to generate your patch(es).
-However, regardless of what tools you use, you should always generate your
-patches using the "unified" diff/patch format and the patches should always
-apply to the libseccomp source tree using the following command from the top
-directory of the libseccomp sources:
-
-	# patch -p1 < changes.patch
-
-If you are not using git, stacked git (stgit), or some other tool which can
-generate patch files for you automatically, you may find the following command
-helpful in generating patches, where "libseccomp.orig/" is the unmodified
-source code directory and "libseccomp/" is the source code directory with your
-changes:
-
-	# diff -purN libseccomp.orig/ libseccomp/
-
-When in doubt please generate your patch and try applying it to an unmodified
-copy of the libseccomp sources; if it fails for you, it will fail for the rest
-of us.
-
 ## Explain Your Work
 
 At the top of every patch you should include a description of the problem you
@@ -120,7 +97,37 @@ your real name, saying:
 
 	Signed-off-by: Random J Developer <random@developer.example.org>
 
-## Email Your Patch(es)
+You can add this to your commit description in `git` with `git commit -s`
+
+## Post Your Patches Upstream
+
+The libseccomp project accepts both GitHub pull requests and patches sent via
+the mailing list.  GitHub pull requests are preferred.  This sections below
+explain how to contribute via either method. Please read each step and perform
+all steps that apply to your chosen contribution method.
+
+### Submitting via Email
+
+Depending on how you decided to work with the libseccomp code base and what
+tools you are using there are different ways to generate your patch(es).
+However, regardless of what tools you use, you should always generate your
+patches using the "unified" diff/patch format and the patches should always
+apply to the libseccomp source tree using the following command from the top
+directory of the libseccomp sources:
+
+	# patch -p1 < changes.patch
+
+If you are not using git, stacked git (stgit), or some other tool which can
+generate patch files for you automatically, you may find the following command
+helpful in generating patches, where "libseccomp.orig/" is the unmodified
+source code directory and "libseccomp/" is the source code directory with your
+changes:
+
+	# diff -purN libseccomp.orig/ libseccomp/
+
+When in doubt please generate your patch and try applying it to an unmodified
+copy of the libseccomp sources; if it fails for you, it will fail for the rest
+of us.
 
 Finally, you will need to email your patches to the mailing list so they can
 be reviewed and potentially merged into the main libseccomp repository.  When
@@ -132,3 +139,7 @@ a problem with your email client.  When in doubt try a test first by sending
 yourself an email with your patch and attempting to apply the emailed patch to
 the libseccomp repository; if it fails for you, it will fail for the rest of
 us trying to test your patch and include it in the main libseccomp repository.
+
+### Submitting via GitHub
+
+See [this guide](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) if you've never done this before.