adding an event of deleting bash history

[h4l0gen]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
this event will trigger rule Delete_or_rename_shell_history
Which issue(s) this PR fixes:

Fixes #105

Special notes for your reviewer:

[h4l0gen]

@FedeDP as expected this rule iss triggered in above terminal when attempted by event-generator in terminal below.

[FedeDP]

I don't think we should remove the user bash_history file :/
first of all this CANNOT be accepted by any user, moreover this is not idempotent since the second time one runs it it will fail to generate a Falco event because the file is not present anymore.
The rule (https://github.com/falcosecurity/rules/blob/main/rules/falco-incubating_rules.yaml#L1017) just checks that either we rename or remove a file whose name ends in ash_history, therefore there is no need to actually delete user bash_history, we can just create a file named ash_history anywhere (in a temp folder) and then remove it.

[h4l0gen]

@FedeDP I was thinking about renaming .bash_history file but that will create problem of second time one runs it it will fail to generate a Falco event because the file is not present anymore as you sugegsted, So going with way you suggested would be great. I will make change in it ASAP!!

[h4l0gen]

I changed event as per @FedeDP suggestions. And this event triggered related rule.

[FedeDP]

Left a suggestion.
Also, is this still wip?

[FedeDP]

/approve

[poiana]

LGTM label has been added.

Git tree hash: 4b3efb2b121100ab9171a77128af265398739d2e

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeDP, h4l0gen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment