crowdstrike / chef-falcon Goto Github PK

Currently, we only support API install method. Need to support Local file installations as well.

A recent introduction to the sensor installer API query results in broken responses due to existing code not accounting for s390x.

Create test suite with Chef InSpec

Ensure existing workflow supports windows os

Add the backend option to the falcon_config role

should include automation to do the following

• create a github release
• update changelog
• update cookbook version based on changes since previous release
  • metadata.rb
  • changelog
  • version used for User-Agent header

Based on CrowdStrike/ansible_collection_falcon#323

tags seem to just keep appending. Guessing the logic of checking the array is off.

• About should include link
• Should probably have a link badge
• tbd

add workflow that will be used to test changes introduced via PR's

https://supermarket.chef.io/cookbooks/falcon#quality

We need to find a way to query the API (if possible, with the existing helper functions) to pull down a specific version that matches the passed in value for version_decrement.

For best practice, we should be using our Falcon GPG keys to install our Linux packages.

Hi Team,
We are having issue with installing crowstrike via chef recipe on rhel 7 where it is failing to meet dependencies, error is below.

STDERR: warning: /opt/CrowdStrike/sensor_installer: Header V4 RSA/SHA512 Signature, key ID xxxxxx: NOKEY
error: Failed dependencies:
    libc.so.6(GLIBC_2.2)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
    libc.so.6(GLIBC_2.2.3)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
    libdl.so.2(GLIBC_2.2)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
    libm.so.6(GLIBC_2.2)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
    libpthread.so.0(GLIBC_2.2)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
    librt.so.1(GLIBC_2.2)(64bit) is needed by falcon-sensor-6.49.0-14606.el7.s390x
---- End output of ["rpm", "-U", "--oldpackage", "/opt/CrowdStrike/sensor_installer"] ----

Looks issue was encountered for ansible as well and that has been fixed.

Thanks,