Dear Wei, You will need hardcoded NIDs for many protocols implemented in OpenSSL (TLS, PKCS12).
For most other purposes the dynamic allocation of objects using OBJ_ functions works fine, but some years ago I had problems with some applications when I used engine that allocated objects dynamically. I hope that it was my fault. On Fri, Dec 23, 2016 at 5:28 AM, Wei, Changzheng <changzheng....@intel.com> wrote: > It works. Thanks a lot! > > > > *From:* openssl-dev [mailto:openssl-dev-boun...@openssl.org] *On Behalf > Of *Peter Waltenberg > *Sent:* Friday, December 23, 2016 8:56 AM > > *To:* openssl-dev@openssl.org > *Subject:* Re: [openssl-dev] Add a new algorithm in "crypto" dir, how to > add the source code into the build system > > > > It's changed in recent OpenSSL. > > 1.1.0c the directories are in Configure. > > # Top level directories to build > $config{dirs} = [ "crypto", "ssl", "engines", "apps", "test", "util", > "tools", " > fuzz" ]; > # crypto/ subdirectories to build > $config{sdirs} = [ > "objects", > "md2", "md4", "md5", "sha", "mdc2", "hmac", "ripemd", "whrlpool", > "poly1305" > , "blake2", > "des", "aes", "rc2", "rc4", "rc5", "idea", "bf", "cast", "camellia", > "seed", > "chacha", "modes", > "bn", "ec", "rsa", "dsa", "dh", "dso", "engine", > "buffer", "bio", "stack", "lhash", "rand", "err", > "evp", "asn1", "pem", "x509", "x509v3", "conf", "txt_db", "pkcs7", > "pkcs12", > "comp", "ocsp", "ui", > "cms", "ts", "srp", "cmac", "ct", "async", "kdf", "sha3" <==== Added > sha3 to the list > ]; > > Persist, it can be done but there was quite a bit of trial and error > before I got it working. > > Peter > > > > From: "Wei, Changzheng" <changzheng....@intel.com> > To: "openssl-dev@openssl.org" <openssl-dev@openssl.org> > Date: 23/12/2016 10:41 > Subject: Re: [openssl-dev] Add a new algorithm in "crypto" dir, > how to add the source code into the build system > Sent by: "openssl-dev" <openssl-dev-boun...@openssl.org> > ------------------------------ > > > > > Hi > Thanks for your reply. > My question is that, I add a new subdir(named *abc*) in openssl/crypto/ > *abc*, and implement codes , Makefile and build.info in the crypt/abc > directory, but when I re-build OpenSSL, I found that this new added sub dir > is not involved into the build system, any source file in this subdir is > not compiled. So I want to know how to compile these new added files in > OpenSSL build system. > > Thanks > > *From:* openssl-dev [mailto:openssl-dev-boun...@openssl.org > <openssl-dev-boun...@openssl.org>] *On Behalf Of *Short, Todd > * Sent:* Friday, December 23, 2016 5:14 AM > * To:* openssl-dev@openssl.org > * Subject:* Re: [openssl-dev] Add a new algorithm in "crypto" dir, how to > add the source code into the build system > > Easiest way is to fork the OpenSSL Github repo and then clone it down to > your local machine where you can do the work locally. Once you are happy, > push it back up to your forked Github repo, and then make a pull request > back to the OpenSSL repo. > > There are lots of places you can get information on git and Github; but > this list isn’t one of them. > -- > -Todd Short > // tsh...@akamai.com > // "One if by land, two if by sea, three if by the Internet." > > On Dec 22, 2016, at 8:12 AM, Wei, Changzheng <changzheng....@intel.com> > wrote: > > Hi, > I want to implement some new algorithm. To make my future work smoothly, I > want to add a new algorithm method like “RSA_METHOD” in OpenSSL framework > so as to I can use an “engine” to support such algorithm. > So I add a new subdir in “crypto” and implement the code and build.inforefer > to “crypto/rsa”. > My question is how to add my new source code into the build system? > > Thanks in advance! > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > > > > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > > -- SY, Dmitry Belyavsky
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
