use more system keyrings to verify arm64 kdump kernel image signature
Get series with b4
b4 am YlOAvM4qpSlHczOd@MiWiFi-R3L-srvVersions newest first · linked by author and title
- v5 Latest posting 2/20 of 3 patches 0 repliesNew
- v5 posting 1/20 of 3 patches 0 repliesSuperseded
- v4 posting 2/20 of 3 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v4 posting 1/2 | 0 of 3 patches | 0 replies | Superseded |
Patches in v5 posting 2/2 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Serge Hallyn |
|---|---|
| Series | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v5 0/3] use more system keyrings to verify arm64 kdump kernel image signature
Quoted 9 lines · Michal Such?nek
Quoted 8 lines · Baoquan He
Hi Coiby,
Quoted 5 lines · Coiby Xu
Currently, a problem faced by arm64 is if a kernel image is signed by a MOK key, loading it via the
kexec_file_load()system call would be rejected with the error "Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7".
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
This patch set allows arm64 to use more system keyrings to verify kdump kernel image signature by making the existing code in x64 public.
Thanks for updating. It would be great to tell why the problem is met, then allow arm64 to use more system keyrings can solve it.
The reason is that MOK keys are (if anywhere) linked to the secondary keyring, and only primary keyring is used on arm64.
Thanks for explaining. This is valuable information and should be put into log for better understanding when reviewing or reading code later.