Date: Sat, 9 Oct 2004 07:12:04 -0700 From: Randy Bush <randy@psg.com> To: Jose M Rodriguez <josemi@freebsd.jazztel.es> Cc: freebsd-gnome@freebsd.org Subject: Re: Gnome2 hangs on startup Message-ID: <16743.61876.660465.143923@ran.psg.com> References: <4166D58D.6020305@ev.net> <opsfkp4emw9aq2h7@mezz.mezzweb.com> <16743.60507.600537.599188@ran.psg.com> <200410091555.07963.josemi@freebsd.jazztel.es>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> It's in our FAQ: http://www.freebsd.org/gnome/docs/faq2.html#q20 >> it all looks reasonable until one gets to >> Fam also requires that portmapper is running. Add the >> appropriate entry to /etc/rc.conf: >> due to long, and possibly outdated, training in security paranoia, >> i just can't bring myself to enable portmapper. >> do i need re-education, or should i hope that this can be changed >> in the future? > Ah. You have problems with inetd/rpcbind/fam security in a machine that > runs X. What special security enabled version of X are you using? engineering is, among other things, compromise. and security is never absolute. i am willing to accept the risks of X in exchange for the benefits, which are considerable. last i talked to security friends, portmapper had fewer benefits and greater risks. ymmv; i do have friends that still use screen. if portmapper's risks have been significantly reduced, plese send clue. otherwise, discussing other security issues would seem to be a red herring. randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16743.61876.660465.143923>