|Subject||Re: [Firebird-Architect] External engines - security|
>> I suggest to stop here - if you want to discuss Firebird'd security inSorry, I don't see how you came to this conclusion here...
>> general (and what you show is a column-level permissions on the metadata
>> objects), create a separate thread and invite Red Soft into it, they
>> have a lot of input for the topic.
> Yes, Roman, I also suggest to stop here.
> It's impossible to extend the engine for external procedures with
> current FB security handling.
I only wanted to say that security in general is to wide topic to try to
fix it within the external procedures. I still think that external
procedures can be added to the engine with the current state of security
and later improved when we touch the security part. So basically, we
consciously decide that external procedures will have same security as
UDFs, but people will have the external procedures.