13e48ead92
- Use the keying module, that was introduced in forgejo/forgejo#5041, to store action secrets safely and securely in the database. - Introduce a central function that sets the secret, `SetSecret` and let the caller do the update call. This is similar to how the twofactor (TOTP) models does it. Ref. https://codeberg.org/forgejo/forgejo/pulls/6074 - Add a relaxed migration, that is run inside a transaction. If it cannot decrypt a action secret, then it's deleted. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/8692 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Gusted <postmaster@gusted.xyz> Co-committed-by: Gusted <postmaster@gusted.xyz>
14 lines
264 B
YAML
14 lines
264 B
YAML
-
|
|
id: 1
|
|
owner_id: 2
|
|
repo_id: 1
|
|
name: SECRET_1
|
|
data: 02458e5f341b2d5081a31283559843b6b7543ab98ed213d2b15b5cef94385fa348afa7e0875122e9
|
|
created_unix: 1753556968
|
|
-
|
|
id: 2
|
|
owner_id: 2
|
|
repo_id: 1
|
|
name: BADBAD
|
|
data: badbad
|
|
created_unix: 1753556968
|