Project

General

Profile

Actions
Copy link

action #164982

open

Implement check that changes in https://progress.opensuse.org/issues/164150 are not used in official product

Added by jsegitz 5 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
jlausuch
Category:
New test
Target version:
-
Start date:
2024-08-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Slack discussion: https://suse.slack.com/archives/C03G45KTP6W/p1722850993683269

Summary: Stagings for SLFO don't use the official key, so secure boot doesn't work. Fabian came up with a workaround.
For stagings a firmware is used that accepts the components signed with the unofficial key.

Ask: Have a test that ensures that for SLFO non-staging environments these keys are not accepted.

Take one of the binaries signed by the unofficial key and try to use it, it should fail

Related issues 1 (0 open — 1 closed)

Related to openQA Tests (public) - action #164150: [SLFO] Stagings: official SUSE keys aren't used anymoreResolvedjlausuch2024-07-18

Actions
Actions
Copy link
 #1

Updated by okurz 5 months ago

  • Project changed from openQA Project (public) to openQA Tests (public)
  • Category set to New test
  • Assignee set to jlausuch

@jlausuch this seems to be related to your recent work, isn't it?

Actions
Copy link
 #2

Updated by okurz 5 months ago

  • Related to action #164150: [SLFO] Stagings: official SUSE keys aren't used anymore added
Actions
Copy link
 #3

Updated by szarate 5 months ago

We need to follow up on how to verify that we have the right keys for the Staging and Product Increments

Actions
Copy link

Also available in: Atom PDF