Re: import/export of large objects on server-side

Поиск
Список
Период
Сортировка
От Klaus Reger
Тема Re: import/export of large objects on server-side
Дата
Msg-id 61010.193.158.34.193.1005926533.squirrel@emailbox24.de
обсуждение исходный текст
Ответ на Re: import/export of large objects on server-side  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: import/export of large objects on server-side  (Karel Zak <zakkr@zf.jcu.cz>)
Список pgsql-hackers
> "Klaus Reger" <K.Reger@twc.de> writes:
>> I've made a patch, that introduces an entry in the PostgreSQL-config
>> file. You can set a drirectory, where all imports/exports can happen.
>> If nothing is set (the default), no imports/exports on the server-side
>> are allowed. To enhance the security, no reading/writung is allowed
>> from/to non-regular files (block-devs, symlinks, etc.)
>
> This is trivially defeatable, assuming that the "import/export"
> directory is world writable (if it isn't, importing will be tough).
...
> While you could patch around these particular attacks by further
> restricting the filenames, the bottom line is that server-side LO
> operations are just inherently insecure.
>
>             regards, tom lane

Ok, you're right, but is it acceptable, to configure this, using the
configfile, rather than with a compile-option?

Regards, Klaus




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Paolo Cassago
Дата:
Сообщение: Btree doesn't work with ">" condition
Следующее
От: Kevin Jacobs
Дата:
Сообщение: Re: Plpython crashing the backend in one easy step - fix