[Bug 214914] [patch] security/libssh2: update 1.8.0

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214914

            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 at FreeBSD.org
          Reporter: citrin+pr at citrin.ru
             Flags: maintainer-feedback?(sbz at FreeBSD.org)
          Keywords: patch
          Assignee: sbz at FreeBSD.org

Created attachment 177493
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=177493&action=edit
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 option
in my patch because it is not clear how to do this in backward compatible way.

Given that now there are three crypto backends we can write something like:
OPTIONS_SINGLE=         CRYPTO
OPTIONS_SINGLE_CRYPTO=  OPENSSL GCRYPT MBEDTLS
OPTIONS_DEFAULT+= OPENSSL

But if libssh2 was build with GCRYPT option on update option dialog will be
shown with OPENSSL option selected by default. If BATCH=yes is used port update
will stop with error. I think it is better to not add new crypto backed (while
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/

-- 
You are receiving this mail because:
You are the assignee for the bug.