raito/lanzaboote
0
0
Fork 0
Code Issues 45 Pull requests 6 Projects Releases 6 Packages Wiki Activity Actions

RISC-V support #28

New issue
Open
opened 2022-12-21 03:36:52 +00:00 by RaitoBezarius · 3 comments
RaitoBezarius commented 2022-12-21 03:36:52 +00:00 (Migrated from github.com)
Copy link

I want SecureBoot on RISC-V, that's all.

I want SecureBoot on RISC-V, that's all.
RaitoBezarius commented 2022-12-21 03:37:25 +00:00 (Migrated from github.com)
Copy link
  • OVMF support in nixpkgs
  • QEMU test support
  • Lanzatool/Lanzaboote support
- [ ] OVMF support in nixpkgs - [ ] QEMU test support - [ ] Lanzatool/Lanzaboote support
RaitoBezarius commented 2023-01-02 01:47:15 +00:00 (Migrated from github.com)
Copy link

I will receive my VF2 on 5 Jan. apparently, will see how hard is it to setup at least a remote builder for software and even a testbed (???).

I will receive my VF2 on 5 Jan. apparently, will see how hard is it to setup at least a remote builder for software and even a testbed (???).
sreehax commented 2024-04-06 07:11:21 +00:00 (Migrated from github.com)
Copy link

Part of the trouble will be in compiling rust onto riscv uefi. I have tried this in the past, and the issue I ran into was that LLVM did not seem to want to build a RISC-V PE/COFF object file at all. The only workarounds for this are either 1. fix LLVM or 2. actually create a riscv ELF binary, but create a faux COFF header with assembly that jumps to the ELF code. This is what the linux kernel uses to boot as EFISTUB on arm64. All of this work will probably fall onto uefi-rs (https://github.com/rust-osdev/uefi-rs/issues/241).
References:
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/kernel/head.S
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/arch/arm64/booting.rst

Part of the trouble will be in compiling rust onto riscv uefi. I have tried this in the past, and the issue I ran into was that LLVM did not seem to want to build a RISC-V PE/COFF object file at all. The only workarounds for this are either 1. fix LLVM or 2. actually create a riscv ELF binary, but create a faux COFF header with assembly that jumps to the ELF code. This is what the linux kernel uses to boot as EFISTUB on arm64. All of this work will probably fall onto uefi-rs (https://github.com/rust-osdev/uefi-rs/issues/241). References: [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/kernel/head.S [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/arch/arm64/booting.rst
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
test
qm3ster/patch-1
blitz/npins
enroll-keys
github-actions
systemd-sb-enroll
fix-ci
bump-edk2
global-credentials
signing-client
in-memory-assembling
cpio-packing
uboot
netboot
experiment-sd-addons
insecure-boot
refactor-building
tpm2-pcr-sections
bootsplash
sd-stub-dtb
bzimage-load
configuration-limit-test
boot-file-integrity-investigation
crane-uefi
v0.4.2
v0.4.1
v0.4.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
bug

Something isn't working

  
dependency

Issues related to our dependencies

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
review-next

   
security

   
stub

   
tool

   
wontfix

This will not be worked on

No labels
bug
dependency
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
review-next
security
stub
tool
wontfix
Milestone
Clear milestone
No items
No milestone
Release 2.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: raito/lanzaboote#28
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?