Date: Mon, 1 Jun 2015 09:34:40 -0700 (PDT) From: Roger Marquis <marquis@roble.com> To: freebsd-security <freebsd-security@freebsd.org> Subject: Re: avoiding base openssl when building ports In-Reply-To: <CA%2B7WWSc47cH_C%2BJCFNv22onuf-V=mFNQ%2BU96Gx_vUm-1YU2OdQ@mail.gmail.com> References: <201506010138.t511cp2P088983@gw.catspoiler.org> <alpine.GSO.1.10.1506011214350.22210@multics.mit.edu> <CA%2B7WWSc47cH_C%2BJCFNv22onuf-V=mFNQ%2BU96Gx_vUm-1YU2OdQ@mail.gmail.com>
| previous in thread | raw e-mail | index | archive | help
Kimmo Paasiala: > Rumour is that something like that is going to happen with all of the > problematic libraries by making them private. If someone with inside > knowledge could confirm these rumours? ;) Curious why this is a rumor? Open source operating systems should be developed transparently, shouldn't they? > This leads to another question. Where is the line going to be drawn > which libraries in the base system should be private? There are > certainly some of them that have to be public like libc and the > support libraries like libusb. There is certainly no sense in making > the ports system use full set of its own libraries for everything > either. I'd be happy just to to 'make buildworld -DWITHOUT_OPENSSL'. Roger Marquis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>