Subject | Re: [firebird-support] Re: Windows security problems. Need permissions help!!!! |
---|---|
Author | Helen Borrie |
Post date | 2004-10-27T23:39:36Z |
At 10:43 PM 27/10/2004 +0000, you wrote:
as well (there should be an uninstall script there to help with this...)
this. The plan for 1.5 was to make it so that the default install created
the firebird user in the OS and then proceeded to give that use a limited
set of OS privileges so that it, and only it, would own the services. This
worked beautifully on the **ix/ux platforms. Except possibly Alex, who
wrote the README and also the Linux SS installer kit, but not the Windows
installer, nobody I know of actually ever got it to work on Windows.
The localsystem user on Windows 2K, XP and Server2000 has much more
extensive privileges than its predecessor of the same name on NT4, Win 9x
(dunno about ME). Localsystem on the later platforms even has some privs
that Administrator can't get.
I get the impression that some intense knowledge is needed of the actual
privs involved (and probably of the gazillion "security patches" that have
been added to Win32 in the past 18 months!!) I kinda think you might be
shooting arrows at a balloon.
However, that said, I guess you are remembering to use the -login switch
when you run instsvc install for the non-localsystem user?
./heLen
>So I uninstalled FB, deleted the install follders and restarted myThis isn't a clean install. You would have needed to run instsvc -remove
>computer.
as well (there should be an uninstall script there to help with this...)
>I reinstalled FB and reset one of the services to run asOK, I'm only one veteran, but I'll give you a bit of background on
>system (it still listed .\firebird) and rebooted again and still I
>cannot access any fdb files, the one that I created and the ones in
>the examples folder. I am kind of discouraged at this point and I am
>hoping that list veterans could help. Thanks!
this. The plan for 1.5 was to make it so that the default install created
the firebird user in the OS and then proceeded to give that use a limited
set of OS privileges so that it, and only it, would own the services. This
worked beautifully on the **ix/ux platforms. Except possibly Alex, who
wrote the README and also the Linux SS installer kit, but not the Windows
installer, nobody I know of actually ever got it to work on Windows.
The localsystem user on Windows 2K, XP and Server2000 has much more
extensive privileges than its predecessor of the same name on NT4, Win 9x
(dunno about ME). Localsystem on the later platforms even has some privs
that Administrator can't get.
I get the impression that some intense knowledge is needed of the actual
privs involved (and probably of the gazillion "security patches" that have
been added to Win32 in the past 18 months!!) I kinda think you might be
shooting arrows at a balloon.
However, that said, I guess you are remembering to use the -login switch
when you run instsvc install for the non-localsystem user?
./heLen