Tarantool development patches archive
 help / color / mirror / Atom feed
From: Ilya Markov <imarkov@tarantool.org>
To: georgy@tarantool.org
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] [security 0/3] System space access check lists
Date: Thu, 29 Mar 2018 10:36:58 +0300	[thread overview]
Message-ID: <cover.1522308989.git.imarkov@tarantool.org> (raw)

branch: gh-3250-system-space-access

Ilya Markov (2):
  box: Add system view for _sequence system space
  security: Refactor reads from systems spaces

imarkov (1):
  security: Refactor system space access checks

 src/box/alter.cc                   | 283 +++++++++++++++++++++++--------------
 src/box/bootstrap.snap             | Bin 1504 -> 1540 bytes
 src/box/index.cc                   |   1 +
 src/box/lua/schema.lua             | 123 +++++++++-------
 src/box/lua/space.cc               |   2 +
 src/box/lua/upgrade.lua            |  34 +++--
 src/box/schema.cc                  | 119 +++++++++++++++-
 src/box/schema.h                   |  28 +++-
 src/box/schema_def.h               |   2 +
 src/box/space.c                    |   3 +-
 src/box/space.h                    |  17 ++-
 src/box/sysview_engine.c           |   4 +
 src/box/sysview_index.c            |  80 ++++++++---
 src/box/user.cc                    |   4 -
 src/box/user.h                     |   7 +
 test/app-tap/tarantoolctl.test.lua |   4 +-
 test/box-py/bootstrap.result       |  11 +-
 test/box/access.result             |  95 ++++++++-----
 test/box/access.test.lua           |  48 ++++---
 test/box/access_bin.result         |   8 +-
 test/box/access_misc.result        |  51 +++++--
 test/box/access_misc.test.lua      |  11 +-
 test/box/access_sysview.result     |  88 ++++++++++--
 test/box/access_sysview.test.lua   |  34 ++++-
 test/box/alter.result              |   3 +
 test/box/net.box.result            |   6 +
 test/box/net.box.test.lua          |   2 +
 test/box/on_replace.result         |  12 +-
 test/box/role.result               |  27 +++-
 test/box/role.test.lua             |  13 +-
 test/box/sequence.result           |  17 ++-
 test/box/sequence.test.lua         |  10 +-
 test/box/transaction.result        |   8 +-
 test/engine/iterator.result        |   2 +-
 test/engine/savepoint.result       |  12 +-
 test/engine/truncate.result        |   2 +-
 test/xlog/upgrade.result           |  11 +-
 37 files changed, 843 insertions(+), 339 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-03-29  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  7:36 Ilya Markov [this message]
2018-03-29  7:36 ` [tarantool-patches] [security 1/3] box: Add system view for _sequence system space Ilya Markov
2018-03-29  7:37 ` [tarantool-patches] [security 2/3] security: Refactor reads from systems spaces Ilya Markov
2018-05-13 12:49   ` [tarantool-patches] " Konstantin Osipov
2018-03-29  7:37 ` [tarantool-patches] [security 3/3] security: Refactor system space access checks Ilya Markov
2018-04-03 14:01 ` [tarantool-patches] Re: [security 0/3] System space access check lists Georgy Kirichenko
  -- strict thread matches above, loose matches on Subject: below --
2018-03-28  8:09 [tarantool-patches] " Ilya Markov

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=cover.1522308989.git.imarkov@tarantool.org \
    --to=imarkov@tarantool.org \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [security 0/3] System space access check lists' \
    /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