From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Ilya Markov <imarkov@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] security: Use system views instead of system spaces
Date: Fri, 8 Jun 2018 06:57:39 +0300 [thread overview]
Message-ID: <20180608035739.GH6866@chai> (raw)
In-Reply-To: <5aec875966ff843a32b03cf9d0e7c85e4fec7f20.1528128037.git.georgy@tarantool.org>
* Georgy Kirichenko <georgy@tarantool.org> [18/06/04 23:48]:
> From: Ilya Markov <imarkov@tarantool.org>
>
> System views are used instead of direct reads of corresponding system
> spaces to explore all accessible objects such as spaces, functions, users
> and e.g. An operation with an inaccessible object produces a 'not found'
> error even if the object exists.
>
> In scope of #3250
>
> Includes up fixes from Georgy
Pushed.
One minor comment, why do we take into account PRIV_X when allow
reads from _vsequence view?
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
prev parent reply other threads:[~2018-06-08 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 16:02 [tarantool-patches] " Georgy Kirichenko
2018-06-08 3:57 ` Konstantin Osipov [this message]
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=20180608035739.GH6866@chai \
--to=kostja@tarantool.org \
--cc=imarkov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] security: Use system views instead of system spaces' \
/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