BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] sandboxing web browsers
- Subject: [Discuss] sandboxing web browsers
- From: jabr at blu.org (John Abreau)
- Date: Mon, 22 Jun 2015 12:19:31 -0400
- In-reply-to: <55881E79.7010207@gmail.com>
- References: <558420D5.6090803@mattgillen.net> <55858DB0.4080709@mattgillen.net> <li6egl6t9pp.fsf@panix5.panix.com> <5586ED60.5070809@gmail.com> <5586F69C.5040702@gmail.com> <55870F2C.8000004@gmail.com> <5587105F.5040305@gmail.com> <55877515.5070004@gmail.com> <55881E79.7010207@gmail.com>
So your point is that some developers create piss-poor Docker deployments, and therefore Docker is a piece of shit?. That logic could be applied to any development system. I've seen plenty of piss-poor coding done in perl, python, C, Fortran, and every other language I've ever reviewed. That fact that an incompetent buffoon can misuse a tool to create badly designed software does not mean that it's impossible for a skilled programmer to use the tool correctly to create well-designed software. On Mon, Jun 22, 2015 at 10:40 AM, Richard Pieri <richard.pieri at gmail.com> wrote: > On 6/21/2015 10:38 PM, Tom Metro wrote: > >> The Docker daemon runs as root. If the non-privileged user starting FF >> is put in the docker group and allowed to start any container, then yes, >> they have root. If instead a SetUID script or sudo rule is used to >> launch a specific container, which does not launch a root shell, then >> the resulting container and FF process won't have root privileges. >> > > Docker requires root to initialize containers. It's how Docker was > designed. It's a known design flaw and the Docker folks have gone on record > stating that they don't intend to fix it. So, if you're going to let me > start Docker containers then I will be able to elevate myself to root on > the host. The only way to stop me is not to let me start Docker containers > at all. > > > Docker does not work "perfectly well" in the first place in my experience. >>> >> >> That may very well be your experience. But some of us use it daily and >> find that it does the intended job. >> > > FSVO "intended". My experience is that developers have been using Docker > to rationalize piss-poor deployment practices. It doesn't matter to them if > their run time environments are utter hell for users to recreate, just put > it all in a container and copy the hell everywhere. > > One most egregious example that I've had to deal with, a project called > ShareLaTeX, their environments are so bad that their containers are the > only supported way of deploying. So bad that their containers don't work > outside of their own environments. > > -- > Rich P. > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6
- Follow-Ups:
- [Discuss] sandboxing web browsers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] sandboxing web browsers
- References:
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- From: me at mattgillen.net (Matthew Gillen)
- [Discuss] memory management
- From: smallm at panix.com (Mike Small)
- [Discuss] sandboxing web browsers
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] sandboxing web browsers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] sandboxing web browsers
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] sandboxing web browsers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] sandboxing web browsers
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] sandboxing web browsers
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] memory management
- Prev by Date: [Discuss] A laptop for Linux
- Next by Date: [Discuss] sandboxing web browsers
- Previous by thread: [Discuss] sandboxing web browsers
- Next by thread: [Discuss] sandboxing web browsers
- Index(es):