>To be serious, yes things could be done a bit differently but this >solution requires the least architectural review and meets user needs >without being too complicated.
How does this change affect or add time to the architectural review? Would it make sense for me to submit a proposal for a future release. I'm not trying to be critical, but here's the problem that I have. Back in 2005, Glenn Burnette wrote a Sun Blueprints paper discussing the practice of limiting privileges in Apache (or other services) and the advantages of Solaris security compared to other platforms. http://www.sun.com/blueprints/0505/819-2680.pdf So it's a little disappointing when I see one or two Coolstack applications that don't even adhere to conventions that were set forth years ago. -- This message posted from opensolaris.org
