gitocean

Files

T

GustedandGusted 4e83f85b75 feat: use keying for webhook secrets (#10059 )

- Follow up of forgejo/forgejo!5041, forgejo/forgejo!6074, forgejo/forgejo!8692, forgejo/forgejo!9923
- The `webhook` table contains a encrypted header authorization.
- Use `keying` to safely store this secret and bound them to the table, column and row id
- The migration isn't spectacular but does closely follow what we learned in the previous three migrations: use a transaction and delete records when you can't decrypt them.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10059
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Reviewed-by: oliverpool <oliverpool@noreply.codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>

2025-12-22 15:51:37 +01:00

assignee_test.go

chore: branding import path (#7337 )

2025-03-27 19:40:14 +00:00

assignee.go

chore: branding import path (#7337 )

2025-03-27 19:40:14 +00:00

comments_test.go

feat: use keying for webhook secrets (#10059 )

2025-12-22 15:51:37 +01:00

comments.go

chore(cleanup): replaces unnecessary calls to formatting functions by non-formatting equivalents (#7994 )