Re:Running Forth Unikernels
by externalreality on Monday April 01, 2019 @10:02PM
(#19550384)
The kernel is small so security patches and such will be less frequent and there are minimal utilities like ssh, shell, what have you.
Also, the key is that there is very little to exploit so the likely hood of it being exploited is reduced.
I'm all for attack surface reduction, but little to exploit is not nothing to exploit. Your shell, sshd, and networking stack have probably all been exploited many times.
Re:Running Forth Unikernels
by externalreality on Wednesday April 03, 2019 @06:43AM
(#19562272)
> Your shell, sshd, and networking stack have probably all been exploited many times.
Yes, I've exploited them myself with script-kiddy tools. Its not hard. Remember those your average libos application may not have any of those things (if not only an simple IP stack).
"can access any file or privilege resources belonging to the unikernel"
What resources?
Network sockets, files, capabilities, any sort of privilege checked object the kernel supplies. It depends on the OS.
Additionally, I think that unikernels are less secure if anything. If you break into the application you are already in kernel mode and can access any file or privilege resources belonging to the unikernel. Also, there is no hope for defense in depth techniques like sandboxing or resource brokers. With a normal application you would need to do some sort of privilege escalation or sandbox escape after hacking the application.