Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org, "n.pettik" <korablev@tarantool.org>
Cc: Kirill Shcherbatov <kshcherbatov@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 2/9] box: fix _trigger and _ck_constraint access check
Date: Fri, 22 Mar 2019 12:29:00 +0300	[thread overview]
Message-ID: <410708e1-331b-fd3a-ab61-459ebbf82ceb@tarantool.org> (raw)
In-Reply-To: <29CE984E-A6A6-4E1D-AFFD-721477BD73B1@tarantool.org>

I do not see fixes for the comments below.

On 11/03/2019 22:29, n.pettik wrote:
> 
>> src/box/alter.cc | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/src/box/alter.cc b/src/box/alter.cc
>> index 0589c9678..ab3dd2e22 100644
>> --- a/src/box/alter.cc
>> +++ b/src/box/alter.cc
>> @@ -3521,6 +3521,11 @@ on_replace_dd_trigger(struct trigger * /* trigger */, void *event)
>> 		uint32_t space_id =
>> 			tuple_field_u32_xc(old_tuple,
>> 					   BOX_TRIGGER_FIELD_SPACE_ID);
>> +		struct space *space = space_by_id(space_id);
>> +		assert(space != NULL);
>> +		access_check_ddl(space->def->name, space->def->id,
>> +				 space->def->uid, SC_SPACE, PRIV_A);
> 
> Why did you check only alter privilege? On drop we should check
> drop privilege, on alter - alter privilege and on creation - creation
> privilege.
> 
> This particular branch processes drop case, so we should use PRIV_D.
> 
>> +
>> 		char *trigger_name =
>> 			(char *)region_alloc_xc(&fiber()->gc,
>> 						trigger_name_len + 1);
>> @@ -3574,6 +3579,10 @@ on_replace_dd_trigger(struct trigger * /* trigger */, void *event)
>> 				  "trigger space_id does not match the value "
>> 				  "resolved on AST building from SQL");
>> 		}
>> +		struct space *space = space_by_id(space_id);
>> +		assert(space != NULL);
>> +		access_check_ddl(space->def->name, space->def->id,
>> +				 space->def->uid, SC_SPACE, PRIV_A);
> 
> And PRIV_C depending on situation.
> 
> The same for _fk_constraint space.
> 
>> @@ -4018,6 +4031,10 @@ on_replace_dd_fk_constraint(struct trigger * /* trigger*/, void *event)
>> 			space_cache_find_xc(fk_def->child_id);
>> 		struct space *parent_space =
>> 			space_cache_find_xc(fk_def->parent_id);
>> +		access_check_ddl(child_space->def->name, child_space->def->id,
>> +				 child_space->def->uid, SC_SPACE, PRIV_A);
>> +		access_check_ddl(parent_space->def->name, parent_space->def->id,
>> +				 parent_space->def->uid, SC_SPACE, PRIV_A);
>> 		struct fkey *old_fkey =
>> 			fkey_grab_by_name(&child_space->child_fkey,
>> 					  fk_def->name);
> 
> Please, add tests on these cases.
> 
> 

  reply	other threads:[~2019-03-22  9:29 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  8:59 [tarantool-patches] [PATCH v2 0/9] sql: Checks on server side Kirill Shcherbatov
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 1/9] box: fix upgrade script for _fk_constraint space Kirill Shcherbatov
2019-03-11 18:44   ` [tarantool-patches] " n.pettik
2019-03-13 11:36   ` Kirill Yukhin
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 2/9] box: fix _trigger and _ck_constraint access check Kirill Shcherbatov
2019-03-11 19:29   ` [tarantool-patches] " n.pettik
2019-03-22  9:29     ` Vladislav Shpilevoy [this message]
2019-03-26 10:59     ` Kirill Shcherbatov
2019-04-01 14:06       ` n.pettik
2019-03-13 11:38   ` Kirill Yukhin
2019-03-13 11:44     ` Kirill Yukhin
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 3/9] box: fix Tarantool upgrade from 2.1.0 to 2.1.1 Kirill Shcherbatov
2019-03-12 11:45   ` [tarantool-patches] " n.pettik
2019-03-20 15:12     ` n.pettik
2019-03-20 15:38       ` Kirill Shcherbatov
2019-03-21 15:23         ` n.pettik
2019-03-21 15:36           ` Vladislav Shpilevoy
2019-03-22  9:28         ` Vladislav Shpilevoy
2019-03-22 10:18           ` Kirill Shcherbatov
2019-03-22 10:21             ` Vladislav Shpilevoy
2019-03-26  9:52   ` Kirill Yukhin
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 4/9] box: fix on_replace_trigger_rollback routine Kirill Shcherbatov
2019-03-11 20:00   ` [tarantool-patches] " n.pettik
2019-03-13 11:39   ` Kirill Yukhin
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 5/9] schema: add new system space for CHECK constraints Kirill Shcherbatov
2019-03-22  9:29   ` [tarantool-patches] " Vladislav Shpilevoy
2019-03-22  9:52     ` n.pettik
2019-03-26 10:59     ` Kirill Shcherbatov
2019-04-01 19:45       ` n.pettik
2019-04-16 13:51         ` Kirill Shcherbatov
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 6/9] sql: disallow use of TYPEOF in Check Kirill Shcherbatov
2019-03-26 10:59   ` [tarantool-patches] " Kirill Shcherbatov
2019-04-01 19:52     ` n.pettik
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 7/9] sql: refactor sqlite3_reset routine Kirill Shcherbatov
2019-03-26 10:59   ` [tarantool-patches] " Kirill Shcherbatov
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 8/9] box: exported sql_bind structure and API Kirill Shcherbatov
2019-03-26 10:59   ` [tarantool-patches] " Kirill Shcherbatov
2019-01-30  8:59 ` [tarantool-patches] [PATCH v2 9/9] sql: run check constraint tests on space alter Kirill Shcherbatov
2019-03-26 10:59   ` [tarantool-patches] " Kirill Shcherbatov
2019-04-02 14:14     ` n.pettik
2019-04-16 13:51       ` Kirill Shcherbatov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=410708e1-331b-fd3a-ab61-459ebbf82ceb@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=kshcherbatov@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v2 2/9] box: fix _trigger and _ck_constraint access check' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox