Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SGX packages #71529

Closed
wants to merge 4 commits into from
Closed

Conversation

exFalso
Copy link
Contributor

@exFalso exFalso commented Oct 21, 2019

Motivation for this change

This PR adds packages related to Intel SGX, in particular the driver, aesmd, and an enclave signing tool. Furthermore a protobuf version was added(3.0) required to run the aesmd daemon.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions: Arch Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @bjornfor @peti

@exFalso
Copy link
Contributor Author

exFalso commented Oct 21, 2019

The elf2sgxs tool requires a nightly rustc version, for which I added the mozilla overlay. I think this is what's causing the CI failure. Any ideas on what to do with this?

@exFalso
Copy link
Contributor Author

exFalso commented Oct 24, 2019

I removed the elf2sgxs tool, it's a bit of an overkill to add a nightly rust version just for that. Perhaps first we should have proper nightly support

Copy link
Contributor

@bjornfor bjornfor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why you added me as reviewer, but this looks good to me :-)

nixos/modules/hardware/intel-sgx.nix Outdated Show resolved Hide resolved
nixos/modules/services/hardware/intel-aesmd.nix Outdated Show resolved Hide resolved
nixos/modules/services/hardware/intel-aesmd.nix Outdated Show resolved Hide resolved
nixos/modules/services/hardware/intel-aesmd.nix Outdated Show resolved Hide resolved
nixos/modules/services/hardware/intel-aesmd.nix Outdated Show resolved Hide resolved
intel-aesmd2_4_0 = callPackage ../os-specific/linux/intel-aesmd/2.4.0.nix { };
intel-aesmd2_5_0 = callPackage ../os-specific/linux/intel-aesmd/2.5.0.nix { };
intel-aesmd2_6_0 = callPackage ../os-specific/linux/intel-aesmd/2.6.0.nix { };
intel-aesmd2_7_0 = callPackage ../os-specific/linux/intel-aesmd/2.7.0.nix { };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the many different versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The protocol has changed through these versions, and the latest release of https://crates.io/crates/aesm-client which interfaces with aesmd only works up to 2.4.0. This is why I added these alternative versions and not just the latest one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Than I only would add 2.4 and the latest.

pkgs/top-level/all-packages.nix Show resolved Hide resolved
@exFalso
Copy link
Contributor Author

exFalso commented Nov 7, 2019

@infinisil anything else I can do for this PR?


patchelf \
--set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)" \
--set-rpath ${lib.makeLibraryPath (with pkgs; [ stdenv.cc.cc.lib openssl protobuf3_0 ])}:$AESM_PATH \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it not possible to compile it from source?

@Profpatsch
Copy link
Member

(triage) what’s the status?

boot.initrd.prepend = mkOrder 1 [ "${pkgs.microcodeIntel}/intel-ucode.img" ];
})

(mkIf (intel.sgx.enable || intel.aesmd.enable) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can aesmd be used without sgx? If not, then you should add an assertion like aesmd.enable -> sgx.enable and change this here to mkIf sgx.enable

@infinisil
Copy link
Member

Also #71529 (comment) should be addressed

@stale
Copy link

stale bot commented Jul 25, 2020

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jul 25, 2020
@Profpatsch
Copy link
Member

Profpatsch commented Jul 28, 2020

@infinisil do you think we could still merge this? It would be sad for the initial and the review work to go to waste.

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jul 28, 2020
@infinisil
Copy link
Member

I don't think it makes sense to merge something that apparently nobody needs as of now (otherwise we'd have seen somebody pinging this PR). The work isn't lost imo because whoever needs it in the future can pick up this PR's work again :). I'll close this for now then

@infinisil infinisil closed this Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants