[prev in list] [next in list] [prev in thread] [next in thread]
List: openssl-dev
Subject: Re: [openssl-dev] About Chinese crypto-algorithms
From: Dmitry Belyavsky <beldmit () gmail ! com>
Date: 2016-09-28 12:49:46
Message-ID: CADqLbzLPaMDsOeJ5NqjY1hFrxm-4mota8qN_yqNt8Gje786w1A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello Robin,
On Wed, Sep 28, 2016 at 3:44 PM, Salz, Rich <rsalz@akamai.com> wrote:
> (I subscribed you to openssl-dev; I hope it works.)
>
> ISO standards are "pay to play." That is, any member organization can get
> something as an ISO standard with not much effort. :)
>
> >> "I strongly recommend that if anyone works on this, they do it as an
> externally-provided ENGINE, like GOST. "
> > Again, I'm sorry I have not a clear notion about the difference
> between build-in approach, and certainly we will take this if necessary.
>
> >> "We may also not have the resources to tackle something that would
> otherwise be of interest (we have a back catalog of nice-to-have
> cryptography waiting for a rainy day)"
> > We certainly respect policy within community and be willing to
> participate in this if possible in all aspects.
>
> You will have to learn how to write an ENGINE. It is possible; Dmitry did
> it for GOST (look in the mailing list archives, https://mta.openssl.org,
> for some details; also maybe the Git log. Also maybe he'll reply to this
> post :) Richard Levitte has started a blog series on writing an ENGINE,
> see https://www.openssl.org/blog/blog/categories/engine-corner/
Sure. I'll be glad to assist.
>
> We want to make it easier to add new crypto via ENGINES. Each time
> someone does it, we learn more about what's needed, the documentation gets
> (a little) better, and so on.
>
>
The best solution will be providing a skeleton engine (with a skeleton
Makefile example).
--
SY, Dmitry Belyavsky
[Attachment #5 (text/html)]
<div dir="ltr">Hello Robin,<div class="gmail_extra"><br><div class="gmail_quote">On \
Wed, Sep 28, 2016 at 3:44 PM, Salz, Rich <span dir="ltr"><<a \
href="mailto:rsalz@akamai.com" target="_blank">rsalz@akamai.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">(I subscribed you to openssl-dev; I hope it works.)<br> \
<br> ISO standards are "pay to play." That is, any member organization can get \
something as an ISO standard with not much effort. :)<br> <span class=""><br>
>> "I strongly recommend that if anyone works on this, they do it as an \
externally-provided ENGINE, like GOST. "<br> </span>> Again, I'm \
sorry I have not a clear notion about the difference between build-in approach, and \
certainly we will take this if necessary.<br> <span class=""><br>
>> "We may also not have the resources to tackle something that would \
otherwise be of interest (we have a back catalog of nice-to-have cryptography waiting \
for a rainy day)"<br> </span>> We certainly respect policy within \
community and be willing to participate in this if possible in all aspects.<br> <br>
You will have to learn how to write an ENGINE. It is possible; Dmitry did it for \
GOST (look in the mailing list archives, <a href="https://mta.openssl.org" \
rel="noreferrer" target="_blank">https://mta.openssl.org</a>, for some details; also \
maybe the Git log. Also maybe he'll reply to this post :) Richard Levitte has \
started a blog series on writing an ENGINE, see <a \
href="https://www.openssl.org/blog/blog/categories/engine-corner/" rel="noreferrer" \
target="_blank">https://www.openssl.org/blog/<wbr>blog/categories/engine-corner/</a></blockquote><div><br></div><div>Sure. \
I'll be glad to assist. </div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> We want to \
make it easier to add new crypto via ENGINES. Each time someone does it, we learn \
more about what's needed, the documentation gets (a little) better, and so \
on.<br> <div class="HOEnZb"><div \
class="h5"><br></div></div></blockquote><div><br></div><div>The best solution will be \
providing a skeleton engine (with a skeleton Makefile example).</div></div><br \
clear="all"><div><br></div>-- <br><div class="gmail_signature" \
data-smartmail="gmail_signature">SY, Dmitry Belyavsky</div> </div></div>
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic