Date: Wed, 10 Aug 2011 22:22:54 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Lars Engels <lars.engels@0x20.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Capsicum project: Ideas needed Message-ID: <alpine.BSF.2.00.1108102222130.75067@fledge.watson.org> In-Reply-To: <769b9c9ca386e2a2b43c27a8fb5e1ff7@mail.0x20.net> References: <4E167C94.70300@kibab.com> <4E1685D8.403@gmail.com> <2c9d3cc8a0b85313f55f53ca573af81a.squirrel@zugang.kibab.com> <769b9c9ca386e2a2b43c27a8fb5e1ff7@mail.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Aug 2011, Lars Engels wrote: > I just stumbled upon this rather outdated thread... > > On Fri, 8 Jul 2011 15:09:52 +0400, Ilya Bakulin wrote: [...] >>> wget curl links/lynx >> This is Ports software, we may try to modify it and even send patches to >> upstream, or maintain our local patches. I wanted to focus on base system >> components during GSoC, but it doesn't hurt to try to capsicumize these >> tools either. > > fetch(1) is similar to wget and curl and is part of the base system, so > would this be a candidate? I'd think fetch would be quite a good candidate -- most of its work is done as a pipeline between a socket and a file, and sandboxing the gubbins that sits in the middle of that pipeline would be quite beneficial. Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1108102222130.75067>