Hello Timo, or anyone else affected, Accepted openssl into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g- 1ubuntu4.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: openssl (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1594748 Title: CRYPTO_set_mem_functions() is broken Status in OpenSSL: Unknown Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Xenial: Fix Committed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 openssl: Installed: 1.0.2g-1ubuntu4.1 Candidate: 1.0.2g-1ubuntu4.1 Version table: *** 1.0.2g-1ubuntu4.1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.2g-1ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages CRYPTO_set_mem_functions() always returns 0 because library initialization already calls CRYPTO_malloc() and disables it: #0 CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x7ffff70ae02c "fips_drbg_lib.c", line=line@entry=106) at mem.c:329 #1 0x00007ffff70596df in FIPS_drbg_new (type=type@entry=0, flags=flags@entry=0) at fips_drbg_lib.c:106 #2 0x00007ffff705aeb9 in FIPS_drbg_health_check ( dctx=dctx@entry=0x7ffff731c960 <ossl_dctx>) at fips_drbg_selftest.c:760 #3 0x00007ffff70595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7ffff731c960 <ossl_dctx>, type=<optimized out>, flags=<optimized out>) at fips_drbg_lib.c:94 #4 0x00007ffff6fe38f3 in RAND_init_fips () at rand_lib.c:287 #5 0x00007ffff6f26f7a in OPENSSL_init_library () at o_init.c:119 #6 0x00007ffff7de74ea in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe5e8, env=env@entry=0x7fffffffe5f8) at dl-init.c:72 #7 0x00007ffff7de75fb in call_init (env=0x7fffffffe5f8, argv=0x7fffffffe5e8, argc=1, l=<optimized out>) at dl-init.c:30 #8 _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffffffe5e8, env=0x7fffffffe5f8) at dl-init.c:120 This doesn't happen in upstream OpenSSL or in Debian's OpenSSL. Looking at the patches, this is caused by FIPS_drbg_init() in openssl-1.0.2g-fips.patch: + if (!(dctx->xflags & DRBG_FLAG_TEST)) { + if (!FIPS_drbg_health_check(dctx)) { + FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE); + return 0; + } + } I don't want any FIPS mode enabled though, so does it really even need to call RAND_init_fips() then? To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1594748/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp