On 11/15/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I don't understand why an user can't WILLINGLY (by EXPLICITLY setting an > OPTION) allow a privileged administrator to run PostGre. > It is a MAJOR problem for me, that will force me to use another database > because my database will be on a DVD and I'm not sure that on the PC on > which it will be executed, the user isn't an admin or that I can create an > unprivileged user. To resume, I don't want my user to be unable to run my > application for that. > The persons specifying this option would know perfectly well the risks > linked to it. > I'm starting to think the PostGre developpers think the users are children. > I'm deeply disappointed to be forced to compile my own PostGre and I will > not.
You can do it. Modify the source, it's a one line change. Be grateful that you have this privilege that you would lack with a proprietary database. Running as an administrator isn't a matter of taste, it's fundamentally broken from a security perspective. Just as you are (usually) asked to jump through hoops to break the normal promises that the database provide, you will be asked to do so on this one. If you are unable to make a one line change to the source and rebuild the application then you probably are unable to understand the security implications of your decision. I wouldn't call this treating you like a child, I'd call this expecting you to be an adult. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
