gpg Error Messages While Running YaST Online Update
The SuSE support database has an article about error messages about gpg when running YaST Online Update: http://sdb.suse.de/sdb/en/html/swiegra_you-gpg.html and offers two possible solutions: 1. Start YaST as normal KDE user and enter root password when prompted. 2. Run YaST from an xterm. (The solution does not specify if the intention is to run the ncurses version or to start the X version.) Well, the first solution doesn't help me at all since that is already the way I run YaST and I still get those error messages with YOU. The second solution allows YOU to run, but the xterm window shows an error message for each package basically saying that the signature could not be verified. Note that I do have gpg installed and /root/.gnupg/* looks good to me. Also note that fou4s can run (and check signatures) without complaint. All this makes me wonder if I am having a different problem than the one discussed in the support database. Any thoughts? -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Tue, May 28, 2002 at 08:35:01PM -0500, Robert C. Paulsen Jr. wrote:
The SuSE support database has an article about error messages about gpg when running YaST Online Update:
http://sdb.suse.de/sdb/en/html/swiegra_you-gpg.html
and offers two possible solutions:
1. Start YaST as normal KDE user and enter root password when prompted.
2. Run YaST from an xterm. (The solution does not specify if the intention is to run the ncurses version or to start the X version.)
Well, the first solution doesn't help me at all since that is already the way I run YaST and I still get those error messages with YOU.
Same here.
The second solution allows YOU to run, but the xterm window shows an error message for each package basically saying that the signature could not be verified.
Haven't tried that, but seems I don't need to :-P
Note that I do have gpg installed and /root/.gnupg/* looks good to me. Also note that fou4s can run (and check signatures) without complaint.
All this makes me wonder if I am having a different problem than the one discussed in the support database. Any thoughts?
Me too. I upgraded to KDE 3.0.1 the other day by downloading the rpms and rpm -Uvh --force --nodeps, and subsequently deleting the various mcop/dcop/whatever files, as per Bens nice guide. It works fine (except the fonts started screwing up yesterday) but YOU gives 'couldn't verify signature' errors all over the place. I haven't been messing with gpg at all, so I'm wondering, too... Some insight would be appreciated :) Jon Clausen
On Wed, May 29, 2002 at 08:24:43AM +0200, Jon Clausen wrote:
On Tue, May 28, 2002 at 08:35:01PM -0500, Robert C. Paulsen Jr. wrote:
The SuSE support database has an article about error messages about gpg when running YaST Online Update:
http://sdb.suse.de/sdb/en/html/swiegra_you-gpg.html
and offers two possible solutions:
1. Start YaST as normal KDE user and enter root password when prompted.
2. Run YaST from an xterm. (The solution does not specify if the intention is to run the ncurses version or to start the X version.)
Well, the first solution doesn't help me at all since that is already the way I run YaST and I still get those error messages with YOU.
Same here.
The second solution allows YOU to run, but the xterm window shows an error message for each package basically saying that the signature could not be verified.
Haven't tried that, but seems I don't need to :-P
Note that I do have gpg installed and /root/.gnupg/* looks good to me. Also note that fou4s can run (and check signatures) without complaint.
All this makes me wonder if I am having a different problem than the one discussed in the support database. Any thoughts?
Me too. I upgraded to KDE 3.0.1 the other day by downloading the rpms and rpm -Uvh --force --nodeps, and subsequently deleting the various mcop/dcop/whatever files, as per Bens nice guide. It works fine (except the fonts started screwing up yesterday) but YOU gives 'couldn't verify signature' errors all over the place.
I haven't been messing with gpg at all, so I'm wondering, too...
Some insight would be appreciated :)
The "solution" I am using now is to create the file: /root/.gnupg/options which has as its contents the single line: no-tty This allows YOU to run without producing error messages. I put "solution" in quotes because I think this may simply be masking the real problem which might be that YOU is not using gpg properly and signatures are not being verified. This seems to be only a minor security hole as long as something is done to really fix it fairly soon. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
participants (2)
-
Jon Clausen -
Robert C. Paulsen Jr.