Sign Packages and Linux Repositories with SHA256.

[twa16]

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

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

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Currently, Falco Linux packages are signed with SHA1. This prevents the installation of Falco on high-assurance systems that do not allow for the installation of packages without signatures made using SHA256.

Which issue(s) this PR fixes:

Fixes #1751

Special notes for your reviewer:
The SHA256 algorithms should be well supported by Linux distributions in use today. I do not believe this this will break installs for anyone.

Does this PR introduce a user-facing change?:
Linux packages and repositories that are created with the modified build scripts will have newer signature algorithms.

update: Linux packages are now signed with SHA256

[poiana]

Welcome @twa16! It looks like this is your first PR to falcosecurity/falco 🎉

[flickerfly]

Did CircleCI just fail to return results?

[twa16]

Anything needed from me on this PR?

[leogr]

Closing and re-opening to trigger the CI
/close

[poiana]

@leogr: Closed this PR.

In response to this:

Closing and re-opening to trigger the CI
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leogr]

/reopen

[poiana]

@leogr: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leogr]

/milestone 0.31.0

[flickerfly]

Looks like the one fail here is also on the main branch right now so probably no related to the PR.

[leogr]

Looks like the one fail here is also on the main branch right now so probably no related to the PR.

#1764 should address the failing test. Let's wait for it.

[leogr]

Hey @twa16

#1764 has been merged into master. Could you rebase on master? 🙏 Once done, the failing test should pass.

[twa16]

@leogr Ok, rebased! Let's see how it goes.

[leogr]

Closing and re-opening to trigger the CI
/close

[poiana]

@leogr: Closed this PR.

In response to this:

Closing and re-opening to trigger the CI
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leogr]

/reopen

[poiana]

@leogr: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[leogr]

LGTM, now!

@twa16 thank you for this PR 🙏

[poiana]

LGTM label has been added.

Git tree hash: f60f9f0e14164f69cce4a38295aca9a6120c459d

[leogr]

/approve
/milestone 0.31.0

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leogr, twa16

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 [leogr]

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