rpm --test --dbpath /tmp/testdb -Uvh *.rpm warning: acl-2.2.7-2.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 warning: basesystem-8.0-2.noarch.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Ive followed previous posts on getting the updated sigs and I dont have any warning with using yum updates. So I am unsure as to why these keys are not on my system.
Heres the install gpg rpms [root@desktop RPMS]# rpm -qa | grep gpg gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-8df56d05-3e828977 gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-1cddbca9-3f9da14c gpg-pubkey-897da07a-3c979a7f gpg-pubkey-e418e3aa-3f439953 gpg-pubkey-897da07a-3c979a7f gpg-pubkey-1cddbca9-3f9da14c gpg-pubkey-a109b1ec-3f6e28d5 gpg-pubkey-8df56d05-3e828977 gpg-pubkey-e418e3aa-3f439953 gpg-pubkey-a109b1ec-3f6e28d5 gpg-pubkey-db42a60e-37ea5438 gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-30c9ecf8-3f9da3f7 gpg-pubkey-db42a60e-37ea5438 gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-30c9ecf8-3f9da3f7 gpg-pubkey-db42a60e-37ea5438 gpg-pubkey-30c9ecf8-3f9da3f7 gpg-pubkey-a109b1ec-3f6e28d5 gpg-pubkey-897da07a-3c979a7f gpg-pubkey-e418e3aa-3f439953 gpg-pubkey-1cddbca9-3f9da14c
Greg said:
rpm --test --dbpath /tmp/testdb -Uvh *.rpm warning: acl-2.2.7-2.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 warning: basesystem-8.0-2.noarch.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Heres the install gpg rpms [root@desktop RPMS]# rpm -qa | grep gpg
These keys are in your regular RPM db, not the database in /tmp/testdb.
On Sun, 11 Jan 2004 16:19:48 -0600, Greg wrote:
rpm --test --dbpath /tmp/testdb -Uvh *.rpm
Why do you "--test" against an RPM database in /tmp/testdb? To test against your regular RPM DB makes much more sense.
warning: acl-2.2.7-2.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 warning: basesystem-8.0-2.noarch.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Ive followed previous posts on getting the updated sigs and I dont have any warning with using yum updates. So I am unsure as to why these keys are not on my system.
Heres the install gpg rpms [root@desktop RPMS]# rpm -qa | grep gpg gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-8df56d05-3e828977 gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-1cddbca9-3f9da14c
-snip-
Unrelated, but:
Many of these are duplicates. I would suggest you remove them all and install each of them only a single time.
ah ok the reason im doing a test is I am building a single cd fedora core load (base+core) with snort, clamav, tripwire, chkrootkit, mondo/mindi, snmp and webmin (with ssl deps). So far its all installing fine and 249 files at 272980k in size for a cd. The only thing left is kickstart automating the configuration to apply the firewall, bastille-linux, and package config changes to make it all tidy.
Since the rpms are in a local directory, I check them to find any dependencies I may have missed and also any problems with bad sigs.
Im going back to 'man rpm' to see if I find out how to tell it to use the regular db as well. But if anyone knows offhand and would post it, that would be great.
thanks,
Greg
On Sun, 2004-01-11 at 17:56, Michael Schwendt wrote:
On Sun, 11 Jan 2004 16:19:48 -0600, Greg wrote:
rpm --test --dbpath /tmp/testdb -Uvh *.rpm
Why do you "--test" against an RPM database in /tmp/testdb? To test against your regular RPM DB makes much more sense.
warning: acl-2.2.7-2.i386.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2 warning: basesystem-8.0-2.noarch.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Ive followed previous posts on getting the updated sigs and I dont have any warning with using yum updates. So I am unsure as to why these keys are not on my system.
Heres the install gpg rpms [root@desktop RPMS]# rpm -qa | grep gpg gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-8df56d05-3e828977 gpg-pubkey-4f2a6fd2-3f9d9d3b gpg-pubkey-1cddbca9-3f9da14c
-snip-
Unrelated, but:
Many of these are duplicates. I would suggest you remove them all and install each of them only a single time.
--
On Sun, 11 Jan 2004 20:08:09 -0600, Greg wrote:
ah ok the reason im doing a test is I am building a single cd fedora core load (base+core) with snort, clamav, tripwire, chkrootkit, mondo/mindi, snmp and webmin (with ssl deps). So far its all installing fine and 249 files at 272980k in size for a cd. The only thing left is kickstart automating the configuration to apply the firewall, bastille-linux, and package config changes to make it all tidy.
Since the rpms are in a local directory, I check them to find any dependencies I may have missed and also any problems with bad sigs.
Im going back to 'man rpm' to see if I find out how to tell it to use the regular db as well. But if anyone knows offhand and would post it, that would be great.
Ehm, to do that you omit the "--dbpath /tmp/testdb" parameter, because by default it will use the regular db in /var/lib/rpm. If you want to install signed packages into your test db, make sure, you import the GPG keys into your test db beforehand.
ok I was using a seperate db because I wanted to ensure that whats installed on my system and what I am checking in a directory are not interfering with each other
On Sun, 2004-01-11 at 23:46, Michael Schwendt wrote:
On Sun, 11 Jan 2004 20:08:09 -0600, Greg wrote:
ah ok the reason im doing a test is I am building a single cd fedora core load (base+core) with snort, clamav, tripwire, chkrootkit, mondo/mindi, snmp and webmin (with ssl deps). So far its all installing fine and 249 files at 272980k in size for a cd. The only thing left is kickstart automating the configuration to apply the firewall, bastille-linux, and package config changes to make it all tidy.
Since the rpms are in a local directory, I check them to find any dependencies I may have missed and also any problems with bad sigs.
Im going back to 'man rpm' to see if I find out how to tell it to use the regular db as well. But if anyone knows offhand and would post it, that would be great.
Ehm, to do that you omit the "--dbpath /tmp/testdb" parameter, because by default it will use the regular db in /var/lib/rpm. If you want to install signed packages into your test db, make sure, you import the GPG keys into your test db beforehand.
--
-
fedora -
Michael Schwendt -
William Hooper