Subject | RE: [firebird-support] Embedded Firebird: Access to UDF library "rfunc.DLL" is denied by server administrator |
---|---|
Author | Helen Borrie |
Post date | 2005-03-31T07:06:16Z |
At 01:05 AM 31/03/2005 -0500, you wrote:
firebird.conf changes to take effect.
UDF access is not restricted.
However, using Full requires you drop all of your UDF declarations and
redeclare them with the fully qualified hard path and file spec declared in
the MODULE_NAME parameter. This of course means you have a database that
will work only on the system it is installed on. I doubt that you want
either this lack of security or the necessary limitations in the database.
declared as rfunc.dll and that it actually works in some other
environment. You're not supposed to include the extension in the
declaration...still, we ARE looking at the Access denied error, not Module
name or entry point not found...
Is it possible that the embedded engine is still loaded in memory when you
test after making these changes?
./hb
>I have tried putting rfunc.dll in the same directory as the dll, then triedYou do know, I suppose, that you would need to unload fbembed.dll for
>putting it in the UDF directory, then in a directory specified in the
>firebird.conf file ... but none of these approaches works.
firebird.conf changes to take effect.
>Currently my firebird.conf file contains the following line:Which is a nonsense. Full doesn't take any arguments, since it signals that
>
> UdfAccess = Full UDF; f:\;
UDF access is not restricted.
However, using Full requires you drop all of your UDF declarations and
redeclare them with the fully qualified hard path and file spec declared in
the MODULE_NAME parameter. This of course means you have a database that
will work only on the system it is installed on. I doubt that you want
either this lack of security or the necessary limitations in the database.
>And there is a file in the f drive:Well, one thing that makes me itchy is that you said you had the module name
>
> F:\rfunc.dll
>
>Ideas?
declared as rfunc.dll and that it actually works in some other
environment. You're not supposed to include the extension in the
declaration...still, we ARE looking at the Access denied error, not Module
name or entry point not found...
Is it possible that the embedded engine is still loaded in memory when you
test after making these changes?
./hb