Re: Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled
От | Tsunakawa, Takayuki |
---|---|
Тема | Re: Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled |
Дата | |
Msg-id | 0A3221C70F24FB45833433255569204D1F63C85A@G01JPEXMBYT05 обсуждение исходный текст |
Ответ на | Re: Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: Re: BUG #13755: pgwin32_is_service not checking if
SECURITY_SERVICE_SID is disabled
|
Список | pgsql-hackers |
From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Michael Paquier > Things are this way since b15f9b08 that introduced pgwin32_is_service(). > Still, by considering what you say, you definitely have a point that if > postgres is started by another service running as Local System logs are > going where they should not. Let's remove the check for LocalSystem but > still check for SE_GROUP_ENABLED. > So, without any refactoring work, isn't the attached patch just but fine? > That seems to work properly for me. Just taking a look at the patch, I'm sure it will work. Committer (Heikki?), v5 is refactored for HEAD, and v6 is for previous releases without refactoring. I'd like v5 to be applied to at least HEAD,as it removes a lot of unnecessary code. Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: