4 ms·
Until there's a local root exploit. ;) My point was simply that this feature carries with it some very large security implications. I'm sure the people develop
by nbpoole 16y ago
Until there's a local root exploit. ;)
My point was simply that this feature carries with it some very large security implications. I'm sure the people developing it are aware of that and will do their best to mitigate any potential issues.
- StavrosK 16y agoOh, of course it does, but I'm sure they do...
- iuguy 16y agoLocal root exploits are few and far between, unless you're running Android.
- kragen 16y agoI wish. I have Ubuntu 10.10, released five months ago, and I already have had to upgrade the kernel four times — because, I believe, of kernel vulnerabilities, most of which I assume are local-root exploits.
- iuguy 16y agoSorry, I was being a bit sarcastic and for that I apologise. Picking Linux kernel vulns is a bit like stealing candy from a baby at the moment due to the way the driver model works. There was an awesome talk about it at dc4420[1] a couple of months back and after some digging I pretty much lost the will to live. Linux Kernel exploits tend to 'return' into root, the vulnerabilities allow them to execute in ring 0 (on x86) which gives them full direct access to the hardware. Think trojaned firmware updates and that's the kind of capability we're talking about, all because users can load and interact with drivers that haven't been maintained for years.
- pedrocr 16y agoIf all you're doing is test-driving applications there won't be any useful data on them. You could just firewall the instances from any other useful stuff and respawn them from scratch every hour. What potential damage do you imagine could be done by rooting them?