Build commands of official openssl package on Ubuntu 18.04
Hi, I'm not sure if this is the right place to ask, I'm sorry if not. I just see this email as the maintainer contact of official openssl package on Ubuntu 18.04. My issue: I am investigate openssl to apply it to encrypt some large files. I want to be able to compile openssl from source (https://github.com/openssl/openssl), since I need to add some debug log and some time-measurement code to observe the performance. I start to build compile with the original source at tag "OpenSSL_1_1_1" follow this instruction: https://www.howtoforge.com/tutorial/how-to-install-openssl-from-source-on-linux/ But when I run some encrypt demo with the new-build openssl, the time consumes to encrypt is somehow bigger than the one with the official openssl package installed by "apt install openssl". I guess that the options of "./config" command are different between 2 openssl builds. My expectation: I hope to find the full build commands (with options for ./config, make) for the official openssl on Ubuntu 18.04, to make sure my self-complied version doesn't change too much from the official. Currently, I can only gleam limited information from the "openssl version -a" command > openssl version -a# The official package OpenSSL 1.1.1 11 Sep 2018 built on: Tue Nov 12 16:58:35 2019 UTC platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-kxN_24/openssl-1.1.1=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 OPENSSLDIR: "/usr/lib/ssl" ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Seeding source: os-specific lap13417@lap13417:~/scratch/openssl$ echo "OpenSSL 1.1.1 11 Sep 2018 > > > /usr/local/ssl/bin/openssl version -a # Self-complied OpenSSL 1.1.1 11 Sep 2018 built on: Mon Mar 16 08:30:17 2020 UTC platform: linux-x86_64 options: bn(64,64) rc4(16x,int) des(int) idea(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DNDEBUG OPENSSLDIR: "/usr/local/ssl" ENGINESDIR: "/usr/local/ssl/lib/engines-1.1" Seeding source: os-specific And again, sorry if I asked at wrong place. Best regards, Dat Le. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [Pkg-openssl-devel] Build commands of official openssl package on Ubuntu 18.04
On Wed, Mar 18, 2020 at 11:03:42AM +, Dat Le wrote: > Hi, > > I'm not sure if this is the right place to ask, I'm sorry if not. I just see > this email as the maintainer contact of official openssl package on Ubuntu > 18.04. > > My issue: > I am investigate openssl to apply it to encrypt some large files. I want to > be able to compile openssl from source (https://github.com/openssl/openssl), > since I need to add some debug log and some time-measurement code to observe > the performance. > I start to build compile with the original source at tag "OpenSSL_1_1_1" > follow this instruction: > https://www.howtoforge.com/tutorial/how-to-install-openssl-from-source-on-linux/ > > But when I run some encrypt demo with the new-build openssl, the time > consumes to encrypt is somehow bigger than the one with the official openssl > package installed by "apt install openssl". > I guess that the options of "./config" command are different between 2 > openssl builds. The config options we use in Debian are: no-idea no-mdc2 no-rc5 no-zlib no-ssl3 enable-unit-test no-ssl3-method enable-rfc3779 enable-cms enable-ec_nistp_64_gcc_128 I assume they are the same in Ubuntu. Only the last one (enable-ec_nistp_64_gcc_128) can have a performance difference, but not to encrypt something, it's related to NIST EC curves. The other difference is that we use -O2 instead of -O3. I doubt it will have an effect. But if you want to try it, just add -O2 to the options. There really isn't any reason why encryption should not have the same performance. I suggest that you verify which shared library you use using ldd, that you pick up the correct version. Kurt -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu Daily MD5 Check
Hi, On Wed, 18 Mar 2020 at 16:59, Newmont wrote: > I have been testing live daily, everyday, on a USB drive for years. About > a month or so ago, I noticed a fsck MD5 checksum being done on every boot > up, checking each package on the USB drive and making the bootup extremely > slow (I know I can bypass with 's'). This check is done on every daily ever > since I noticed it in the first, including today's, daily's bootup and it > persists on different USB drives. > > Is there any plan to remove this feature from future's daily? > It's working as designed. The goal is to ensure the installation media is free of errors prior to an install. As you noticed, you can use 's' to skip the test. We've had significant reports in the past of corrupt files leading to a failed install. This helps reduce the instances of that occuring. More discussion over on the Ubuntu discourse. https://discourse.ubuntu.com/t/defaulting-to-verify-the-image-integrity-before-installing-on-desktop/13472 Cheers, -- Alan Pope Developer Advocate Canonical - Data Center Development +44 (0) 7973 620 164 alan.p...@canonical.com http://ubuntu.com/ -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu Daily MD5 Check
On Wed, Mar 18, 2020 at 04:58:54PM +, Newmont wrote: > I have been testing live daily, everyday, on a USB drive for years. About a > month or so ago, I noticed a fsck MD5 checksum being done on every boot up, > checking each package on the USB drive and making the bootup extremely slow > (I know I can bypass with 's'). This check is done on every daily ever since > I noticed it in the first, including today's, daily's bootup and it persists > on different USB drives. This was discussed here: https://lists.ubuntu.com/archives/ubuntu-devel/2019-November/040844.html https://discourse.ubuntu.com/t/defaulting-to-verify-the-image-integrity-before-installing-on-desktop/13472 signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Ubuntu Daily MD5 Check
I have been testing live daily, everyday, on a USB drive for years. About a month or so ago, I noticed a fsck MD5 checksum being done on every boot up, checking each package on the USB drive and making the bootup extremely slow (I know I can bypass with 's'). This check is done on every daily ever since I noticed it in the first, including today's, daily's bootup and it persists on different USB drives. Is there any plan to remove this feature from future's daily? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
