[CAPI] Wrong expirations for custom blocklists

[blotus]

Custom blocklists allows a different expiration per item, but when pulled through CAPI, the duration is set to 24h globally (because the blocklist format of CAPI does not allow for per-iterm expiration).

This means that any decisions added to a custom blocklist will be kept for at least 24h, and for decisions longer than that, they will be rounded up to the next 24h.

We need a new blocklist format (probably similar to the one used for the allowlists) to better handle custom blocklists.

[github-actions]

@blotus: Thanks for opening an issue, it is currently awaiting triage.

In the meantime, you can:

1. Check Crowdsec Documentation to see if your issue can be self resolved.
2. You can also join our Discord.
3. Check Releases to make sure your agent is on the latest version.

Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[github-actions]

@blotus: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

• /kind feature
• /kind enhancement
• /kind refactoring
• /kind bug
• /kind packaging

Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

[blotus]

/kind bug