search for: nogpg

...at: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig 'filename' If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg 'filename' 10. References: From mail@mail.redhat.com Oct 17:20:32 1999 -0400 Received: (qmail 1551 invoked from network); 21 Oct 1999 21:20:34 -0000 Received: from mail.redhat.com (199.183.24.239) by lists.redhat.com with SMTP; 21 Oct 1999 21:20:34 -0000 Received: from alien.devel.red...

...md systemd-libs-204-9.fc19.x86_64 systemd-python-204-9.fc19.x86_64 systemd-sysv-204-9.fc19.x86_64 systemd-libs-204-9.fc19.i686 systemd-204-9.fc19.x86_64 Here is the scenario I'm trying to go through: $ export LIBVIRT_DEFAULT_URI=lxc:/// $ getenforce Enforcing $ sudo yum -y --releasever=19 --nogpg --installroot=/srv/mycontainer --disablerepo='*' --enablerepo=fedora install systemd passwd yum fedora-release vim-minimal ... lots of output $ ls /srv/mycontainer/ bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var $ cat test2.xml &lt...

...ting by booting the host w/ 'audit=0' on Kernel command line. (NOTE: There's work in progress[2] in upstream Kernel to fix this.) Create container ---------------- On the host, specify an installroot (/srv) and install a minimal Fedora 20 distribution: $ yum -y --releasever=20 --nogpg \ --installroot=/srv/testcontainer \ --disablerepo='*' --enablerepo=fedora \ install systemd passwd yum \ fedora-release vim-minimal Boot into the container, set a password: $ systemd-nspawn -D /srv/testcontainer [. . .] -bash-4.2# passwd Start...

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: Thanks to Brock Tellier at btellier@USA.NET for noting the vulnerability in resend, to Shevek at shevek@anarres.org and Olaf Kirch at okir@monad.swb.de for noting the vulnerability in the wrapper.

...at: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 10. References: CERT Advisory CA-99-13 Multiple Vulnerabilities in WU-FTPD http://www.cert.org AUSCERT Advisory AA-1999.01 ftp://www.auscert.org.au/security/advisory/AA-1999.01.wu-ftpd.mapping_chdir.vul AUSCERT Advisory AA-1999.02 ftp://www.auscert.org.au/security/advisory/AA-1...

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.securityfocus.com/bid/1125 From mail@mail.redhat.com Jun 19:00:12 2000 -0400 Received: (qmail 8172 invoked from network); 15 Jun 2000 23:00:13 -0000 Received: from mail.redhat.com (199.183.24.239) by lists.redhat.com with SMTP; 15 Jun 2000 23:00:1...

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: N/A

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.securityfocus.com/vdb/bottom.html?vid=1547 http://bugs.perl.org/perlbug.cgi?req=tidmids&tidmids=20000806.001 Copyright(c) 2000 Red Hat, Inc. _______________________________________________ Redhat-watch-list mailing list Redhat-watch-list@redhat....

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.openbsd.org/security.html#27 Thanks to Matt Power <mhpower@MIT.EDU> for making us aware of this vulnerability. Copyright(c) 2000 Red Hat, Inc.

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: N/A Copyright(c) 2000 Red Hat, Inc. _______________________________________________ Redhat-watch-list mailing list Redhat-watch-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-watch-list

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: Thanks to Prasanth A. Kumar for pointing this error out. Copyright(c) 2000 Red Hat, Inc.

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.zope.org/Products/Zope/Hotfix_08_09_2000/security_alert Copyright(c) 2000 Red Hat, Inc. _______________________________________________ Redhat-watch-list mailing list Redhat-watch-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-wa...

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: N/A Copyright(c) 2000 Red Hat, Inc.

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: N/A

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: Thanks to Colten Edwards <edwards@bitchx.dimension6.com> for making us aware of the problem.

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: N/A

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.zope.org/Products/Zope/Hotfix_06_16_2000/security_alert

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 10. References: N/A

...: http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 10. References: http://www.securityfocus.com/vdb/bottom.html?vid=1060

...http://www.redhat.com/corp/contact.html You can verify each package with the following command: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 10. References: Cristian - -- - ---------------------------------------------------------------------- Cristian Gafton -- gafton@redhat.com -- Red Hat, Inc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "How could this be a problem...