Closed gkelly closed 3 months ago
Unfortunately I don't think I can accept this patch, as we are required by our Open Source org to provide the source files directly for compliance reasons. But I can look updating the kernel and kernel sources on our end.
Unfortunately I don't think I can accept this patch, as we are required by our Open Source org to provide the source files directly for compliance reasons. But I can look updating the kernel and kernel sources on our end.
That was my suspicion. I think this is a desirable bump because it unlocks building the enclave kernel on modern Ubuntu releases without a builder container or VM.
As we have restructured how the kernels are built in this package and have moved to newer 6.6 based kernels this seems to not be relevant anymore. We still need to pick up the new kernels in aws-nitro-enclaves-cli
though.
Closing.
Issue #, if available: #19
Description of changes: Upgrade kernel to v4.14.314
I understand that the project hosts a mirror of kernel source, so I imagine that the actual fix here will require mirroring the source to the AWS mirror. Might also be worth considering not doing the mirroring, given how few people actually build the NE kernel themselves.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.