2013-08-30 16:09:44 +02:00
|
|
|
config BR2_PACKAGE_LIBSSH2
|
|
|
|
|
bool "libssh2"
|
2017-11-05 22:34:02 +01:00
|
|
|
select BR2_PACKAGE_OPENSSL if !(BR2_PACKAGE_MBEDTLS || BR2_PACKAGE_LIBGCRYPT)
|
2013-08-30 16:09:44 +02:00
|
|
|
help
|
|
|
|
|
libssh2 is a client-side C library implementing the SSH2
|
|
|
|
|
protocol as defined by Internet Drafts: SECSH-TRANS(22),
|
|
|
|
|
SECSH-USERAUTH(25), SECSH-CONNECTION(23), SECSH-ARCH(20),
|
|
|
|
|
SECSH-FILEXFER(06)*, SECSH-DHGEX(04), and SECSH-NUMBERS(10)
|
|
|
|
|
|
|
|
|
|
http://www.libssh2.org/
|
package/libssh2: Add selectable crypto libraries
Currently, the selection of the backend is based on a priority order,
which is not always desirable: not all features are available for all
backends, as reported upstream:
https://github.com/libssh2/libssh2/issues/213
In that particular case, the problem is that libgcrypt is unable to
read encrypted certificates created with openssl, but it is likely
that other incompatibilities exist as well.
As such, allow a user to select the backend most appropriate to their
use-case.
Note that this changes the defaults: previously, if openssl was already
selected and we additionally select libssh2, openssl would be used as
a backend. Now, mbedtls is the default so if the user doesn't change
it, mbedtls will be used.
Signed-off-by: Sam Voss <sam.voss@rockwellcollins.com>
[Arnout: remove now-unneeded comment in .mk file]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-11-01 17:22:56 +01:00
|
|
|
|
|
|
|
|
if BR2_PACKAGE_LIBSSH2
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Crypto Backend"
|
|
|
|
|
help
|
|
|
|
|
Select crypto library to be used in libssh2.
|
|
|
|
|
|
|
|
|
|
config BR2_PACKAGE_LIBSSH2_MBEDTLS
|
|
|
|
|
bool "mbedtls"
|
2017-11-05 22:34:02 +01:00
|
|
|
depends on BR2_PACKAGE_MBEDTLS
|
package/libssh2: Add selectable crypto libraries
Currently, the selection of the backend is based on a priority order,
which is not always desirable: not all features are available for all
backends, as reported upstream:
https://github.com/libssh2/libssh2/issues/213
In that particular case, the problem is that libgcrypt is unable to
read encrypted certificates created with openssl, but it is likely
that other incompatibilities exist as well.
As such, allow a user to select the backend most appropriate to their
use-case.
Note that this changes the defaults: previously, if openssl was already
selected and we additionally select libssh2, openssl would be used as
a backend. Now, mbedtls is the default so if the user doesn't change
it, mbedtls will be used.
Signed-off-by: Sam Voss <sam.voss@rockwellcollins.com>
[Arnout: remove now-unneeded comment in .mk file]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-11-01 17:22:56 +01:00
|
|
|
|
|
|
|
|
config BR2_PACKAGE_LIBSSH2_LIBGCRYPT
|
|
|
|
|
bool "gcrypt"
|
2017-11-05 22:34:02 +01:00
|
|
|
depends on BR2_PACKAGE_LIBGCRYPT
|
package/libssh2: Add selectable crypto libraries
Currently, the selection of the backend is based on a priority order,
which is not always desirable: not all features are available for all
backends, as reported upstream:
https://github.com/libssh2/libssh2/issues/213
In that particular case, the problem is that libgcrypt is unable to
read encrypted certificates created with openssl, but it is likely
that other incompatibilities exist as well.
As such, allow a user to select the backend most appropriate to their
use-case.
Note that this changes the defaults: previously, if openssl was already
selected and we additionally select libssh2, openssl would be used as
a backend. Now, mbedtls is the default so if the user doesn't change
it, mbedtls will be used.
Signed-off-by: Sam Voss <sam.voss@rockwellcollins.com>
[Arnout: remove now-unneeded comment in .mk file]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-11-01 17:22:56 +01:00
|
|
|
|
|
|
|
|
config BR2_PACKAGE_LIBSSH2_OPENSSL
|
|
|
|
|
bool "openssl"
|
2017-11-05 22:34:02 +01:00
|
|
|
depends on BR2_PACKAGE_OPENSSL
|
package/libssh2: Add selectable crypto libraries
Currently, the selection of the backend is based on a priority order,
which is not always desirable: not all features are available for all
backends, as reported upstream:
https://github.com/libssh2/libssh2/issues/213
In that particular case, the problem is that libgcrypt is unable to
read encrypted certificates created with openssl, but it is likely
that other incompatibilities exist as well.
As such, allow a user to select the backend most appropriate to their
use-case.
Note that this changes the defaults: previously, if openssl was already
selected and we additionally select libssh2, openssl would be used as
a backend. Now, mbedtls is the default so if the user doesn't change
it, mbedtls will be used.
Signed-off-by: Sam Voss <sam.voss@rockwellcollins.com>
[Arnout: remove now-unneeded comment in .mk file]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-11-01 17:22:56 +01:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
endif
|
