similar to: [PATCH] builder: Allow GnuPG v2 or v1 to be used (RHBZ#1438939).

All of the GPG commands we run are compatible with either v1 or v2, so this simply involves looking for either gpg2 or gpg binaries at runtime. --- builder/builder.ml | 10 ++++------ builder/cmdline.ml | 8 +++++++- builder/virt-builder.pod | 7 +++++-- docs/guestfs-building.pod | 2 +- 4 files changed, 17 insertions(+), 10 deletions(-) diff --git a/builder/builder.ml

Where do I get an update for gpg2 (GnuPG) for CentOS 6.10 that is compliant with CVE-2018-12020? I'm trying to update gpg2 (GnuPG GNU Privacy Guard) on my fully updated CentOS 6.10 computer to comply with CVE-2018-12020. My system has gpg2 package? gnupg2-2.0.14-8.el6.x86_64.rpm This package does not appear to be compliant with CVE-2018-12020.? I can not find and update anywhere. I have tried

Add sort of "headers" to split most of the logical sections of the configure, so it is easier to get feedback on the progress of configure. --- configure.ac | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/configure.ac b/configure.ac index 7f9c1dac0..5ccf6f821 100644 --- a/configure.ac +++ b/configure.ac @@ -76,11 +76,15 @@

When we are valgrinding we don't really care about the child processes, which might be qemu, libvirtd, etc. So disable tracing into children (at least, as far as is possible with valgrind, which is not entirely disabling it, but suppressing it). --- m4/guestfs_progs.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs_progs.m4 b/m4/guestfs_progs.m4 index

On Tuesday, 4 April 2017 23:13:58 CEST Richard W.M. Jones wrote: > All of the GPG commands we run are compatible with either v1 or v2, so > this simply involves changing the configure script to find either > binary. > --- Why not simply check it at runtime? We have Common_utils.which already. -- Pino Toscano

THINK YOU! I'm from China! but,my network is can &nbsp;reaching http://builder.libguestfs.org/ ------------------&nbsp;原始邮件&nbsp;------------------ 发件人:&nbsp;"rjones"<rjones@redhat.com&gt;; 发送时间:&nbsp;2020年6月23日(星期二) 晚上6:37 收件人:&nbsp;"雁渡寒潭"<chnlcq@qq.com&gt;;"libguestfs"<libguestfs@redhat.com&gt;;

On Tue, Jun 23, 2020 at 06:14:06PM +0800, 雁渡寒潭 wrote: > hello: I yum install libguestfs-tools,when I run virt-builder -l > error: > curl: (56) Recv failure: Connection reset by peer > virt-builder: error: external command ‘'curl' -q --config > '/tmp/virt-builder.sVjrSV/guestfscurl53f9ac.conf'’ exited with error 56 Possibly a problem reaching

On Tue, Sep 26, 2017 at 1:30 PM, Marco Gaiarin via samba < samba at lists.samba.org> wrote: > > [Clearly, this question is intimately connected to the previous...] > > I need a way to ''preprocess'' or at least intercept password changes, > because i need to propagate them to other ''legacy'' systems. > > I've looked around and found

Use ./configure --sysconfdir setting. --- builder/paths.ml | 2 +- mllib/guestfs_config.ml.in | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/builder/paths.ml b/builder/paths.ml index cbd9d4bd0..9ce8504a1 100644 --- a/builder/paths.ml +++ b/builder/paths.ml @@ -35,7 +35,7 @@ let xdg_config_home () = let xdg_config_dirs () = let dirs = try Sys.getenv

Use ./configure --sysconfdir setting. --- builder/paths.ml | 2 +- mllib/guestfs_config.ml.in | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/builder/paths.ml b/builder/paths.ml index cbd9d4bd0..d7c4820bf 100644 --- a/builder/paths.ml +++ b/builder/paths.ml @@ -35,7 +35,7 @@ let xdg_config_home () = let xdg_config_dirs () = let dirs = try Sys.getenv

--- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 188bed76f..1ab54500d 100644 --- a/configure.ac +++ b/configure.ac @@ -94,7 +94,7 @@ dnl Find the release date for this version. This is used in dnl the website 'index.html' file. We have to do this after dnl testing for awk in guestfs_progs.m4 above.

Good Morning-- I'm looking to shore up security in my system and with communications. Can you point me to the proper version of GnuPG for CentOS 5.3 (Final)? Thanks, Dick -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." --Benjamin Franklin 1755

Assorted collection of small improvements in making libguestfs build on non-Linux OSes; most of the changes impact tests though. Thanks, Pino Toscano (7): build: check the path of fuser, and use it in FUSE code tests: move guestfs-md5.sh to test-data v2v: tests: isolate SHA1 calculation in an own shared function v2v: tests: use guestfs-hashsums.sh for MD5 php: pass $(MAKE) to

I've started to sign release tarballs: http://libguestfs.org/download/1.21-development/ The *.tar.gz.sig file is a PGP ASCII-armored signature of the corresponding *.tar.gz file. It is signed using gpg2 with this key: pub 4096R/E1B768A0 2011-10-11 Key fingerprint = F777 4FB1 AD07 4A7E 8C87 67EA 9173 8F73 E1B7 68A0 uid Richard W.M. Jones <rjones at

When running gpg to validate a signature, use also --batch in non-verbose mode to avoid the extra "Good signature" messages that are printed by gpg2 even in quiet mode. We are parsing the status output anyway to check the validation result, so this should be harmless (and the full gpg output is printed in verbose mode anyway). --- builder/sigchecker.ml | 2 +- 1 file changed, 1

>>>>>> On 01/20/2016 01:37 AM, Alice Wonder wrote: >>>>>>> I'm trying to find where / how to use sha256 when I sign packages >>>>>>> but I >>>>>>> am not having much luck. Closest I have found is this : >>>>>>> >>>>>>>

Hi, the libguestfs library uses a number of external tools; for some of them, we search for them at build time, enabling some feature only if found, and later on assuming at runtime they are installed. However, the situation is more complex than that: - hardcoding the full path means that there is an incoherency in the way some of the tools are used, as some other tools (e.g. qemu-img) are

On 01/20/2016 03:32 PM, Alice Wonder wrote: > On 01/20/2016 02:58 AM, Johnny Hughes wrote: >> On 01/20/2016 04:52 AM, Johnny Hughes wrote: >>> On 01/20/2016 04:48 AM, Johnny Hughes wrote: >>>> On 01/20/2016 04:39 AM, Johnny Hughes wrote: >>>>> On 01/20/2016 01:37 AM, Alice Wonder wrote: >>>>>> hi, >>>>>>

While there are input modes that do not use libvirt, making libvirt mandatory for virt-v2v slightly simplifies the code now, and allow for further improvements/integration with libvirt later on. --- Makefile.am | 2 ++ v2v/Makefile.am | 20 ++++++-------------- v2v/libvirt_utils-c.c | 22 ---------------------- v2v/v2v.ml | 12 +++--------- 4 files changed, 11

Hi, the libguestfs library uses a number of external tools; for some of them, we search for them at build time, enabling some feature only if found, and later on assuming at runtime they are installed. However, the situation is more complex than that: - hardcoding the full path means that there is an incoherency in the way some of the tools are used, as some other tools (e.g. qemu-img) are