Adriano dos Santos Fernandes wrote 13.12.2021 12:17:
Database administrator does not always have access to full server.
And database developers create code (or declare external routines) in
database.
In well organized environment they don't. Developers just prepare script that
is applied
On 13/12/2021 07:14, Alex Peshkoff via Firebird-devel wrote:
>> The problem is that if it's available in the server, it can be declared
>> in all databases.
>
> But since v.3 we have control on access to UDR. I suppose DS meant
> something like this:
>
> # ./isql -user guest employee
> Database:
Alex Peshkoff via Firebird-devel wrote 13.12.2021 12:05:
Don't forget about subj: this UDR is needed only to let QA suite to check
exact parameters of Firebird config. It does need "any known setting".
As soon as we put it into our std distro (even as an exanple) it's loosing that
On 12/13/21 14:00, Dimitry Sibiryakov wrote:
Vlad Khorsun wrote 13.12.2021 11:53:
13.12.2021 12:45, Dimitry Sibiryakov пишет:
Vlad Khorsun wrote 13.12.2021 10:32:
Our IFirebirdConf implementation
is not generic enough to provide way to get value of any known
setting as string.
IMHO it
Vlad Khorsun wrote 13.12.2021 11:53:
13.12.2021 12:45, Dimitry Sibiryakov пишет:
Vlad Khorsun wrote 13.12.2021 10:32:
Our IFirebirdConf implementation
is not generic enough to provide way to get value of any known setting as
string.
IMHO it is ok for such UDR to return only subset of
13.12.2021 12:45, Dimitry Sibiryakov пишет:
Vlad Khorsun wrote 13.12.2021 10:32:
Our IFirebirdConf implementation
is not generic enough to provide way to get value of any known setting as
string.
IMHO it is ok for such UDR to return only subset of known parameters
converting them into
Vlad Khorsun wrote 13.12.2021 10:32:
Our IFirebirdConf implementation
is not generic enough to provide way to get value of any known setting as
string.
IMHO it is ok for such UDR to return only subset of known parameters
converting them into strings by hand.
--
WBR, SD.
Alex Peshkoff via Firebird-devel wrote 13.12.2021 11:14:
I suppose DS meant something like this:
# ./isql -user guest employee
Database: employee, User: GUEST
SQL> select sum_args(1,2,3) from rdb$database;
Statement failed, SQLSTATE = 28000
no permission for EXECUTE access to FUNCTION SUM_ARGS
On 12/13/21 12:56, Adriano dos Santos Fernandes wrote:
On 12/12/2021 14:55, Dimitry Sibiryakov wrote:
Alex Peshkoff via Firebird-devel wrote 12.12.2021 18:52:
If it does not return sensitive information, I see no problem in add
it to examples UDR project.
With a check for SYSDBA I see no
On 12/12/2021 14:55, Dimitry Sibiryakov wrote:
> Alex Peshkoff via Firebird-devel wrote 12.12.2021 18:52:
>>>
>>> If it does not return sensitive information, I see no problem in add
>>> it to examples UDR project.
>>
>> With a check for SYSDBA I see no security risk with this UDR
>
> Isn't
11.12.2021 23:01, Alex Peshkoff via Firebird-devel wrote:
I see no big use in full support of v.3. Requested UDR is trivial but I highly displike requirement of keeping it in std distro of
firebird.
I see no problem to add such UDR into samples but, unfortunately, it can't be
implemented
Alex Peshkoff via Firebird-devel wrote 12.12.2021 18:52:
If it does not return sensitive information, I see no problem in add it to
examples UDR project.
With a check for SYSDBA I see no security risk with this UDR
Isn't GRANT EXECUTE to RDB$ADMIN enough? Or UDRs are not subject of SQL
On 12/12/21 01:21, Adriano dos Santos Fernandes wrote:
Em sáb., 11 de dez. de 2021 18:03, Alex Peshkoff via Firebird-devel
escreveu:
I see no big use in full support of v.3. Requested UDR is trivial
but I
highly displike requirement of keeping it in std distro of firebird.
If
12.12.2021 01:21, Adriano dos Santos Fernandes wrote:
If it does not return sensitive information, I see no problem in add it
to examples UDR project.
I like the idea about /examples, but the server configuration *is*
sensitive information, if exposed to a non-DBA user. So the examples
Em sáb., 11 de dez. de 2021 18:03, Alex Peshkoff via Firebird-devel <
firebird-devel@lists.sourceforge.net> escreveu:
> I see no big use in full support of v.3. Requested UDR is trivial but I
> highly displike requirement of keeping it in std distro of firebird.
>
If it does not return sensitive
On 12/10/21 14:41, Pavel Cisar wrote:
Hi all,
our test suite contains many tests that depend on specific server
configuration settings (mostly related to security, encryption, pools,
timeouts, transactions etc.). As these configuration requirements may
contradict each other, it's not
Hi all,
our test suite contains many tests that depend on specific server
configuration settings (mostly related to security, encryption, pools,
timeouts, transactions etc.). As these configuration requirements may
contradict each other, it's not possible to create single firebird.conf
that
17 matches
Mail list logo
