From: Konstantin Osipov <kostja@tarantool.org> To: tarantool-patches@freelists.org Cc: imarkov <imarkov@tarantool.org> Subject: [tarantool-patches] Re: [PATCH 2/3] security: add limits on object_type-privilege pair Date: Fri, 8 Jun 2018 17:01:35 +0300 [thread overview] Message-ID: <20180608140135.GA6436@chai> (raw) In-Reply-To: <0e6cd9bcff2fca4d04105b42f96dd78a3bfee743.1528448404.git.georgy@tarantool.org> * Georgy Kirichenko <georgy@tarantool.org> [18/06/08 12:11]: > From: imarkov <imarkov@tarantool.org> > > Introduce constraints on object_type-privilege pairs. > These constraints limit senseless grants/revokes, i.e., > sequence - execute, all space related privileges(insert, delete, > update), > function - alter, all space related privileges, > role - all privileges except create, drop, alter, execute Sorry for nitpicking, but wouldn't it be better to list allowed privileges rather than forbidden ones? Perhaps making a plain C array which would map object type to the list of allowed bits and exporting it to Lua make things even simpler? > -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2018-06-08 14:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-08 9:06 [tarantool-patches] [PATCH 0/3] Object group privileges Georgy Kirichenko 2018-06-08 9:06 ` [tarantool-patches] [PATCH 1/3] box: Add privilleges constants to lua Georgy Kirichenko 2018-06-08 10:31 ` [tarantool-patches] " Vladislav Shpilevoy 2018-06-08 13:20 ` Konstantin Osipov 2018-06-08 9:06 ` [tarantool-patches] [PATCH 2/3] security: add limits on object_type-privilege pair Georgy Kirichenko 2018-06-08 14:01 ` Konstantin Osipov [this message] 2018-06-08 9:06 ` [tarantool-patches] [PATCH 3/3] Introduce privileges for object groups Georgy Kirichenko 2018-06-08 17:26 ` [tarantool-patches] " Konstantin Osipov
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=20180608140135.GA6436@chai \ --to=kostja@tarantool.org \ --cc=imarkov@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 2/3] security: add limits on object_type-privilege pair' \ /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