Helen,
> To quote the doc in firebird.conf:
>
> "UdfAccess may be None, Full or Restrict. If you choose
> Restrict, provide ';'-separated trees list, where UDF libraries
> are stored. Relative paths are treated relative to RootDirectory entry
> (see above). Default value 'Restrict UDF' provides the same
> restrictions
> as in FB 1.0. To specify access to specific trees, enum all required
> paths (for Win32 this may be something like 'C:\ExternalFunctions',
> for unix - '/db/extern;/mnt/extern')."
>
> Now -
> Does None mean that UDFs are to be disallowed on the server
> altogether?
Yes. The same rule applies to e.g. ExternalFileAccess.
> Default value 'Restrict UDF' or 'Restrict'?
"Restrict UDF", because FB1 has ./UDF directory as a default for the
libraries.
> And, if it's "as in FB 1.0" does this mean the same as
> "Full"? AFAIK, the
> external_function_dir locations had no restrictions...so
> could you explain
> what is meant by Restrict and Full?
None:
- no UDF library can be used at all
Full:
- every UDF library may be used
Restrict <list>:
- only UDF libraries located in <list> may be used
- if no path is specified, the lookup is done in the <list>
I.e. the 'Restrict' option combines both security and search order.
Dmitry
|
