Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "signcryption" #9

Open
ribose-jeffreylau opened this issue Jun 6, 2017 · 4 comments
Open

Support "signcryption" #9

ribose-jeffreylau opened this issue Jun 6, 2017 · 4 comments
Assignees
Milestone

Comments

@ribose-jeffreylau
Copy link
Contributor

ribose-jeffreylau commented Jun 6, 2017

Roadmap #3

https://en.wikipedia.org/wiki/Signcryption

@GildedHonour
Copy link

I'll work on this.

@GildedHonour
Copy link

  1. Signcryption requires an assymetric algorithm, doesn't it? Whereas now transcryptor, at least by default, uses AES which is symmetric one. Should we change that so that it supports only assymetric algorithms?

  2. Will signcryption change the interface for a client? Or will a client use transcryptor the way he uses it now?

@ronaldtse
Copy link
Contributor

@GildedHonour indeed. The current usage of transcryptor is locked into attr-encrypted which relies on the encryptor gem, which in turn relies on OpenSSL.

To enable signcryption we will need to support algorithms beyond those provided by the encryptor gem, that uses non-OpenSSL libraries, such as https://github.com/randombit/botan, for example through https://github.com/riboseinc/ruby-botan.

Signcryption algorithms are also detailed in ISO/IEC 29150:2011 -- Information technology -- Security techniques — Signcryption.

@GildedHonour
Copy link

@ronaldtse ISO/IEC 29150:2011 isn't free and I haven't found a free one in the internet, is there any? Although I have a few pdfs and code in python, maybe that'll be enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants