Date: Mon, 28 Nov 2016 20:30:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214914] [patch] security/libssh2: update 1.8.0 Message-ID: <bug-214914-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214914 Bug ID: 214914 Summary: [patch] security/libssh2: update 1.8.0 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sbz@FreeBSD.org Reporter: citrin+pr@citrin.ru Flags: maintainer-feedback?(sbz@FreeBSD.org) Keywords: patch Assignee: sbz@FreeBSD.org Created attachment 177493 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177493&action= =3Dedit libssh 1.8.0 Please update libssh2 to the latest version - 1.8.0. Patch attached. files/patch-configure is needed to fix build with GCRYPT option (bug fixed = by upstream in git after 1.8.0 release). In 1.8.0 support of mbedTLS backend was added. It was not added as port opt= ion in my patch because it is not clear how to do this in backward compatible w= ay. Given that now there are three crypto backends we can write something like: OPTIONS_SINGLE=3D CRYPTO OPTIONS_SINGLE_CRYPTO=3D OPENSSL GCRYPT MBEDTLS OPTIONS_DEFAULT+=3D OPENSSL But if libssh2 was build with GCRYPT option on update option dialog will be shown with OPENSSL option selected by default. If BATCH=3Dyes is used port = update will stop with error. I think it is better to not add new crypto backed (wh= ile not requested by users), than break existing installations. If there is a backward compatible way to move GCRYPT from OPTIONS_DEFINE to OPTIONS_SINGLE_CRYPTO I'd like to know. Build of port with default options was tested using poudriere: http://poudriere.citrin.ru/data/latest-per-pkg/libssh2/ --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214914-13>