<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">HI Giovanni<div class=""><br class=""></div><div class="">Depending on the country you are located in, you may need to check the current status of your countries regulatory legislation regarding encryption technologies. </div><div class=""><br class=""></div><div class="">Participating countries : <a href="https://www.wassenaar.org/participating-states/" class="">https://www.wassenaar.org/participating-states/</a> [ contacts ] & encryption is listed under Dual List Technologies : <a href="https://www.wassenaar.org/" class="">https://www.wassenaar.org/</a> is always a good place to start before drilling into your own locations specific regulations on encryption technologies.</div><div class=""><br class=""></div><div class="">All the best mate and hoping your invention prospers.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class="">-- <br class=""><br class="">Regards,<br class=""><br class="">Mark A. Lane <br class=""><br class="">© Mark A. Lane 1980 - 2019, All Rights Reserved.<br class="">© FooCrypt 1980 - 2019, All Rights Reserved.<br class="">© FooCrypt, A Tale of Cynical Cyclical Encryption. 1980 - 2019, All Rights Reserved.<br class="">© Cryptopocalypse 1980 - 2019, All Rights Reserved.<br class=""></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 9 Apr 2019, at 03:50, Giovanni Fontana <<a href="mailto:giovanni.fontana72@gmail.com" class="">giovanni.fontana72@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Thank you every one for the answers and tips, really a great and active group!<div class=""><br class=""></div><div class="">Thank you also to Teja and Tobias who has just wrote some suggestion on how I can have a technical shortcut to prove the functionality of my algorithms in very limited environment.</div><div class="">What I asked is to move a first step (after the algorithms) to have a demo before to setup a company. </div><div class="">For my limited knowledge I know the algorithms need to be published and security must be proved for some authorities. All I need to prove is the algorithms works in the real world and openSSL is one of the most used tool to do that, then the other steps</div><div class=""><br class=""></div><div class="">Thank you again for your answer, this is what I really need.</div><div class=""><br class=""></div><div class="">Giovanni</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno lun 8 apr 2019 alle ore 19:23 Teja Prabhu <<a href="mailto:213tej@gmail.com" class="">213tej@gmail.com</a>> ha scritto:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div dir="ltr" class=""><div class="">1. dasync_aes128_cbc_cipher (search for this in <a href="https://github.com/openssl/openssl/blob/master/engines/e_dasync.c" target="_blank" class="">https://github.com/openssl/openssl/blob/master/engines/e_dasync.c</a>) || replace it with your symmetric cipher, and do the same for RSA.</div><div class="">2. setup a server and client and hard-code the symmetric & asymmetric ciphers to your ciphers</div><div class="">3. your idea is simply not going to work. Like Tobias said, you have to add them manually. I suggest you simply not use OpenSSL or any TLS library, unless you have a lot of clout in the International Communication Union.</div><div class=""><br class=""></div><div class="">You can take Mega's approach and use javascript since every browser under the sun has it (as an additional layer over TLS).</div><br clear="all" class=""><div class=""><div dir="ltr" class="gmail-m_-1805954590037411320gmail_signature"><div dir="ltr" class="">Teja Prabhu</div></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 8, 2019 at 7:06 PM Tobias Nießen <<a href="mailto:tniessen@tnie.de" target="_blank" class="">tniessen@tnie.de</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">> creation of x509 certificate with algo1 and algo2, and/or TLS and SSL <br class="">
> connection always with algo1 and algo2<br class="">
As far as I know, you will need to have an OID assigned for each <br class="">
algorithm for x509 certificates. You can add those to OpenSSL manually, <br class="">
but you won't be able to communicate with any other software that does <br class="">
not implement them. (And as Rich said, there is little reason for people <br class="">
to trust and use non-standard algorithms.)<br class="">
</blockquote></div>
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>