HI Giovanni Depending on the country you are located in, you may need to check the current status of your countries regulatory legislation regarding encryption technologies.
Participating countries : https://www.wassenaar.org/participating-states/ <https://www.wassenaar.org/participating-states/> [ contacts ] & encryption is listed under Dual List Technologies : https://www.wassenaar.org/ <https://www.wassenaar.org/> is always a good place to start before drilling into your own locations specific regulations on encryption technologies. All the best mate and hoping your invention prospers. -- Regards, Mark A. Lane © Mark A. Lane 1980 - 2019, All Rights Reserved. © FooCrypt 1980 - 2019, All Rights Reserved. © FooCrypt, A Tale of Cynical Cyclical Encryption. 1980 - 2019, All Rights Reserved. © Cryptopocalypse 1980 - 2019, All Rights Reserved. > On 9 Apr 2019, at 03:50, Giovanni Fontana <giovanni.fontan...@gmail.com> > wrote: > > Thank you every one for the answers and tips, really a great and active group! > > 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. > What I asked is to move a first step (after the algorithms) to have a demo > before to setup a company. > 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 > > Thank you again for your answer, this is what I really need. > > Giovanni > > > > Il giorno lun 8 apr 2019 alle ore 19:23 Teja Prabhu <213...@gmail.com > <mailto:213...@gmail.com>> ha scritto: > 1. dasync_aes128_cbc_cipher (search for this in > https://github.com/openssl/openssl/blob/master/engines/e_dasync.c > <https://github.com/openssl/openssl/blob/master/engines/e_dasync.c>) || > replace it with your symmetric cipher, and do the same for RSA. > 2. setup a server and client and hard-code the symmetric & asymmetric ciphers > to your ciphers > 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. > > You can take Mega's approach and use javascript since every browser under the > sun has it (as an additional layer over TLS). > > Teja Prabhu > > > On Mon, Apr 8, 2019 at 7:06 PM Tobias Nießen <tnies...@tnie.de > <mailto:tnies...@tnie.de>> wrote: > > creation of x509 certificate with algo1 and algo2, and/or TLS and SSL > > connection always with algo1 and algo2 > As far as I know, you will need to have an OID assigned for each > algorithm for x509 certificates. You can add those to OpenSSL manually, > but you won't be able to communicate with any other software that does > not implement them. (And as Rich said, there is little reason for people > to trust and use non-standard algorithms.)