Netboot
31–40 of 48 posts
Re: Netboot
#32Re: Netboot
#33NetBooting from the internet AND over HTTP? Sign me up! Sarcasm aside, at the very least it would have been nice to see it use iPXE's `imgtrust` and `imgverify` functionality, which I could then audit and load on to a boot medium for netboot use.
Re: Netboot
#34NetBooting from the internet AND over HTTP? Sign me up! Sarcasm aside, at the very least it would have been nice to see it use iPXE's `imgtrust` and `imgverify` functionality, which I could then audit and load on to a boot medium for netboot use.
I'm not familiar with these but I saw a commit from just a couple of hours ago referencing "image trust" [1], so maybe it's in the works now following your comment?
[1]: https://github.com/antonym/netboot.xyz/commit/25910be18da219...
Re: Netboot
#35Going signed CA wouldn't be hard to do in this case at all, it's just part of the build process actually but only gets you to to a trusted PXE+menu system. After getting into the PXE menu a system could still hijack the upstream kernel/initrd files.
Even freebsd netinstall (aka not limited to linux installers) is just http/ftp without any package signing. The whole ecosystem probably needs to mature some more in regards to verification that won't break downstream projects such as this.
Re: Netboot
#36Going signed CA wouldn't be hard to do in this case at all, it's just part of the build process actually but only gets you to to a trusted PXE+menu system. After getting into the PXE menu a system could still hijack the upstream kernel/initrd files.
Even freebsd netinstall (aka not limited to linux installers) is just http/ftp without any package signing. The whole ecosystem probably needs to mature some more in regards to verification that won't break downstream projects such as this.
Re: Netboot
#37Re: Netboot
#38Looks similar to boot.rackspace.com.
Re: Netboot
#39Re: Netboot
#40The only thing I get from xyz domains is spam and viruses (I didn't click the link).