From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/3] hw/usb/ccid: remove references to NSS
Date: Wed, 4 Nov 2020 14:47:05 +0100 [thread overview]
Message-ID: <48e24f80-1198-c101-28a8-3bec0318b482@redhat.com> (raw)
In-Reply-To: <20201104131924.593522-2-berrange@redhat.com>
On 11/4/20 2:19 PM, Daniel P. Berrangé wrote:
> The NSS package was previously pre-requisite for building CCID related
> features, however, this became obsolete when the libcacard library was
> spun off to a separate project:
>
> commit 7b02f5447c64d1854468f758398c9f6fe9e5721f
> Author: Marc-André Lureau <marcandre.lureau@redhat.com>
> Date: Sun Aug 30 11:48:40 2015 +0200
>
> libcacard: use the standalone project
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .travis.yml | 14 +++++++-------
> docs/ccid.txt | 15 +++++++--------
> scripts/coverity-scan/coverity-scan.docker | 1 -
> tests/docker/dockerfiles/centos7.docker | 1 +
> tests/docker/dockerfiles/centos8.docker | 1 +
> tests/docker/dockerfiles/fedora.docker | 2 +-
> 6 files changed, 17 insertions(+), 17 deletions(-)
...
> diff --git a/docs/ccid.txt b/docs/ccid.txt
> index c7fda6d07d..1baf03e29b 100644
> --- a/docs/ccid.txt
> +++ b/docs/ccid.txt
> @@ -34,15 +34,14 @@ reader and smart card (i.e. not backed by a physical device) using this device.
>
> 2. Building
>
> -The cryptographic functions and access to the physical card is done via NSS.
> -
> -Installing NSS:
> +The cryptographic functions and access to the physical card is done via the
> +libcacard library, whose development package must be installed prior to
> +building QEMU:
>
> In redhat/fedora:
> - yum install nss-devel
> -In ubuntu/debian:
> - apt-get install libnss3-dev
> - (not tested on ubuntu)
> + yum install libcacard-devel
> +In ubuntu:
> + apt-get install libcacard-dev
>
> Configuring and building:
> ./configure --enable-smartcard && make
> @@ -51,7 +50,7 @@ Configuring and building:
> 3. Using ccid-card-emulated with hardware
>
> Assuming you have a working smartcard on the host with the current
> -user, using NSS, qemu acts as another NSS client using ccid-card-emulated:
> +user, using libcacard, qemu acts as another client using ccid-card-emulated:
Maybe replace 'qemu' by 'QEMU' (another instance line 125).
Otherwise:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Thanks.
next prev parent reply other threads:[~2020-11-04 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 13:19 [PATCH 0/3] Some cleanups to build deps Daniel P. Berrangé
2020-11-04 13:19 ` [PATCH 1/3] hw/usb/ccid: remove references to NSS Daniel P. Berrangé
2020-11-04 13:47 ` Philippe Mathieu-Daudé [this message]
2020-11-04 13:19 ` [PATCH 2/3] tests: remove "bc" from package listing Daniel P. Berrangé
2020-11-04 13:33 ` Philippe Mathieu-Daudé
2020-11-04 13:19 ` [PATCH 3/3] docker: remove libblockdev-mpath-devel package Daniel P. Berrangé
2020-11-04 13:42 ` Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48e24f80-1198-c101-28a8-3bec0318b482@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).