Kris,
Dynamically allocate yourself a block of NIDs, one for each algorithm, using
OBJ_new_nid().
Note also, that there is a preferable option if you are working against the
upcoming 3.0. Instead of developing an engine, create a provider. This avoids
NIDs completely and was designed from
Hello,
I'm working on development of OpenSSL ENGINE that integrates
post-quantum algorithms (new NIDs). During integration I
need to modify OpenSSL code to add custom function, but would
prefer not to need add anything to OpenSSL code (so engine
can be dynmicaly loaded by any modern OpenSSL).
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/
>> creation of x509 certificate with algo1 and algo2, and/or TLS and SSL
>> connection always with algo1 and algo2
Tobias Nießen wrote:
> 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,
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
1. dasync_aes128_cbc_cipher (search for this in
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
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
* Sure, I want to publish the algorithm, but not yet... waiting for
establishing a company.
This is a bit off-topic, but trying to make money from a cryptographic
algorithm isn’t really done any more. RSA was locked up by patents, and there
were some elliptic curve patents that have since
On Mon, Apr 08, 2019 at 05:48:56PM +0200, Giovanni Fontana wrote:
> my name is Giovanni Fontana. I made a new symmetric crypto algorithm (let’s
> call it *algo1*) and a new asymmetric crypto algorithm (let’s call it
> *algo2*).
Recent additions to OpenSSL include X25519, Ed25519 and ChaCha20.
Hi Clarke,
Thanks for the email.
Sure, I want to publish the algorithm, but not yet... waiting for
establishing a company.
For similar reasons no github usage at moment.
Giovanni
Il giorno lun 8 apr 2019 alle 18:06 Dennis Clarke
ha scritto:
> On 4/8/19 11:48 AM, Giovanni Fontana wrote:
> >
On 4/8/19 11:48 AM, Giovanni Fontana wrote:
> Hello everybody,
>
> my name is Giovanni Fontana. I made a new symmetric crypto algorithm
> (let’s call it *algo1*) and a new asymmetric crypto algorithm (let’s
> call it *algo2*).
>
> I use algo2 for key exchange and with that I can create a session
Hello everybody,
my name is Giovanni Fontana. I made a new symmetric crypto algorithm (let’s
call it *algo1*) and a new asymmetric crypto algorithm (let’s call it
*algo2*).
I use algo2 for key exchange and with that I can create a session key to
cipher and decipher with algo1, so Alice and Bob
12 matches
Mail list logo
