Re: Hiding name and version
| От | Quiroga, Damian |
|---|---|
| Тема | Re: Hiding name and version |
| Дата | |
| Msg-id | 5F6634B7560CA34EA814093D8CDACAC736F8D7C1@fmsmsx107.amr.corp.intel.com обсуждение исходный текст |
| Ответ на | Re: Hiding name and version (Jerry Sievers <gsievers19@comcast.net>) |
| Список | pgsql-general |
Good to know. Thanks everyone. -----Original Message----- From: Jerry Sievers [mailto:gsievers19@comcast.net] Sent: Thursday, September 17, 2015 11:03 PM To: Tom Lane Cc: Joshua D. Drake; Quiroga, Damian; pgsql-general@postgresql.org Subject: Re: [GENERAL] Hiding name and version Tom Lane <tgl@sss.pgh.pa.us> writes: > "Joshua D. Drake" <jd@commandprompt.com> writes: > >> On 09/17/2015 10:32 AM, Quiroga, Damian wrote: >>> Is it possible to prevent users from running the "version" function >>> or all system information functions? If so, how? > >> You could probably revoke access to the function(s) (I haven't tried >> it because it seems very silly). > > I believe revoking public execute access would work, but I concur that > this specific request seems entirely pointless. Anyone with SQL-level > access to the server, and a copy of the release notes, can soon > determine what version they are talking to by testing for the presence > or absence of assorted features and bugs. > > Keep in mind also that pg_dump or pg_upgrade would not preserve such > alterations to system functions. And let's not forget... show server_version or server_version_num; Oh, and interactive psql without -q prints server version in the banner :-) > > regards, tom lane -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800
В списке pgsql-general по дате отправления: