chore: improving naming

Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com>

docker/builder/root/usr/bin/entrypoint

@@ -21,7 +21,7 @@ esac
 
 case "$CMD" in
 "cmake")
-    # Check that source directory contains Falco and Sysdig
+    # Check that source directory contains Falco and sysdig
     if [ ! -d "$SOURCE_DIR/sysdig" ]; then
         echo "Missing sysdig source." >&2
         exit 1

docker/builder/root/usr/bin/usage

@@ -17,7 +17,7 @@ How to use.
     * docker run -ti falcosecurity/falco-builder bash
 
     To build Falco it needs:
-    - a bind-mount on the source directory (ie., the directory containing falco and sysdig source as siblings)
+    - a bind-mount on the source directory (ie., the directory containing Falco and sysdig source as siblings)
 
     Optionally, you can also bind-mount the build directory.
     So, you can execute it from the Falco root directory as follows.

docker/rhel/Dockerfile

@@ -1,12 +1,12 @@
 FROM registry.access.redhat.com/rhel7
 
-MAINTAINER Sysdig Support Team <support@sysdig.com>
+LABEL maintainer="opensource@sysdig.com"
 
 ### Atomic/OpenShift Labels - https://github.com/projectatomic/ContainerApplicationGenericLabels
 LABEL name="falco" \
-    vendor="Sysdig" \
+    vendor="falcosecurity" \
     url="http://falco.org/" \
-    summary="Container Native runtime security" \
+    summary="Container native runtime security" \
     description="Falco is an open source project for intrusion and abnormality detection for Cloud Native platforms." \
     run='docker run -d --name falco --restart always --privileged --net host --pid host -v /var/run/docker.sock:/host/var/run/docker.sock -v /dev:/host/dev -v /proc:/host/proc:ro -v /boot:/host/boot:ro -v /lib/modules:/host/lib/modules:ro -v /usr:/host/usr:ro -v /etc:/host/etc:ro --shm-size=350m registry.connect.redhat.com/sysdig/falco'
 

docker/rhel/docker-entrypoint.sh

@@ -18,7 +18,7 @@
 
 # set -e
 
-# Set the SKIP_MODULE_LOAD variable to skip loading the sysdig kernel module
+# Set the SKIP_MODULE_LOAD variable to skip loading the kernel module
 
 if [[ -z "${SKIP_MODULE_LOAD}" ]]; then
     echo "* Setting up /usr/src links from host"

docker/tester/root/usr/bin/entrypoint

@@ -38,7 +38,7 @@ case "$CMD" in
     cd $BUILD_DIR/$BUILD_TYPE/docker/local
     docker build --build-arg FALCO_VERSION="$FALCO_VERSION" -t "$DOCKER_IMAGE_NAME" .
 
-    # Check that source directory contains Falco and Sysdig
+    # Check that source directory contains Falco and sysdig
     if [ ! -d "$SOURCE_DIR/falco/test" ]; then
         echo "Missing $SOURCE_DIR/falco/test directory." >&2
         exit 1

examples/bad-mount-cryptomining/README.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-Based on a [blog post](https://sysdig.com/blog/detecting-cryptojacking/) we wrote, this example shows how an overly permissive container environment can be exploited to install cryptomining software and how use of the exploit can be detected using Sysdig Falco.
+Based on a [blog post](https://sysdig.com/blog/detecting-cryptojacking/) we wrote, this example shows how an overly permissive container environment can be exploited to install cryptomining software and how use of the exploit can be detected using Falco.
 
 Although the exploit in the blog post involved modifying the cron configuration on the host filesystem, in this example we keep the host filesystem untouched. Instead, we have a container play the role of the "host", and set up everything using [docker-compose](https://docs.docker.com/compose/) and [docker-in-docker](https://hub.docker.com/_/docker/).
 

examples/bad-mount-cryptomining/demo.yml

@@ -29,7 +29,7 @@ services:
       - "falco"
 
   falco:
-    image: sysdig/falco:latest
+    image: falcosecurity/falco:latest
     privileged: true
     volumes:
       - docker-socket:/host/var/run

examples/mitm-sh-installer/demo.yml

@@ -38,7 +38,7 @@ attacker_botnet_master:
 # Owned by client, detects attack by attacker
 falco:
   container_name: falco
-  image: sysdig/falco:latest
+  image: falcosecurity/falco:latest
   privileged: true
   volumes:
     - /var/run/docker.sock:/host/var/run/docker.sock

examples/nodejs-bad-rest-api/demo.yml

@@ -9,7 +9,7 @@ express_server:
 
 falco:
   container_name: falco
-  image: sysdig/falco:latest
+  image: falcosecurity/falco:latest
   privileged: true
   volumes:
     - /var/run/docker.sock:/host/var/run/docker.sock

integrations/anchore-falco/README.md

@@ -1,6 +1,6 @@
 # Create Falco rule from Anchore policy result
 
-This integration creates a rule for Sysdig Falco based on Anchore policy result.
+This integration creates a rule for Falco based on Anchore policy result.
 So that when we will try to run an image which has a ```stop``` final action result
 in Anchore, Falco will alert us.
 

integrations/k8s-using-daemonset/k8s-with-rbac/falco-daemonset-configmap-slim.yaml

@@ -39,7 +39,7 @@ spec:
 # Leave blank for the default probe location, or set to the path
 # of a precompiled probe.
 #          env:
-#          - name: SYSDIG_BPF_PROBE
+#          - name: BPF_PROBE
 #            value: ""
           args: [ "/usr/bin/falco", "--cri", "/host/run/containerd/containerd.sock", "-K", "/var/run/secrets/kubernetes.io/serviceaccount/token", "-k", "https://$(KUBERNETES_SERVICE_HOST)", "-pk"]
           volumeMounts:

integrations/k8s-using-daemonset/k8s-with-rbac/falco-daemonset-configmap.yaml

@@ -23,7 +23,7 @@ spec:
 # Leave blank for the default probe location, or set to the path
 # of a precompiled probe.
 #          env:
-#          - name: SYSDIG_BPF_PROBE
+#          - name: BPF_PROBE
 #            value: ""
           args: [ "/usr/bin/falco", "--cri", "/host/run/containerd/containerd.sock", "-K", "/var/run/secrets/kubernetes.io/serviceaccount/token", "-k", "https://$(KUBERNETES_SERVICE_HOST)", "-pk"]
           volumeMounts: