From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org Cc: kostja@tarantool.org Subject: [tarantool-patches] [PATCH 0/2] swim crypto Date: Tue, 14 May 2019 00:57:13 +0300 [thread overview] Message-ID: <cover.1557784472.git.v.shpilevoy@tarantool.org> (raw) This patchset is a full duplicate of the previously sent version to help Kostja to review it. Note, that these two commits are going to be kept even if lib/crypto will be totally refactored after Georgy review. Probably a third one will be added to support arbitrary encryption algorithms and make packet size dynamic. Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-3234-swim-crypto Issue: https://github.com/tarantool/tarantool/issues/3234 Vladislav Shpilevoy (2): swim: split send/recv into phases swim: implement and expose transport-level encryption src/lib/swim/CMakeLists.txt | 2 +- src/lib/swim/swim.c | 12 ++ src/lib/swim/swim.h | 15 +++ src/lib/swim/swim_ev.h | 2 + src/lib/swim/swim_io.c | 258 ++++++++++++++++++++++++++++++------ src/lib/swim/swim_io.h | 26 +++- src/lib/swim/swim_proto.h | 5 + test/unit/swim.c | 47 ++++++- test/unit/swim.result | 9 +- test/unit/swim_test_utils.c | 15 ++- test/unit/swim_test_utils.h | 8 ++ 11 files changed, 349 insertions(+), 50 deletions(-) -- 2.20.1 (Apple Git-117)
next reply other threads:[~2019-05-13 21:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-13 21:57 Vladislav Shpilevoy [this message] 2019-05-13 21:57 ` [tarantool-patches] [PATCH 1/2] swim: split send/recv into phases Vladislav Shpilevoy 2019-05-13 21:57 ` [tarantool-patches] [PATCH 2/2] swim: implement and expose transport-level encryption Vladislav Shpilevoy -- strict thread matches above, loose matches on Subject: below -- 2019-04-29 18:13 [tarantool-patches] [PATCH 0/2] swim crypto Vladislav Shpilevoy
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.1557784472.git.v.shpilevoy@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='Re: [tarantool-patches] [PATCH 0/2] swim crypto' \ /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