[Bug 647169] New: simplify that geeky gpg key dialog.
https://bugzilla.novell.com/show_bug.cgi?id=647169 https://bugzilla.novell.com/show_bug.cgi?id=647169#c0 Summary: simplify that geeky gpg key dialog. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: crrodriguez@novell.com QAContact: qa@suse.de Found By: Community User Blocker: --- Hi: The gpg key dialog in zypper is a royal pain the ass. ;) ------------------ -------------------------------------- Se ha recibido una nueva clave firmada para el repositorio o paquete: ID de clave: BED1E87979EAFD54 Nombre de la clave: security OBS Project <security@build.opensuse.org> Huella digital: 74848501FA390C473AFDAC38BED1E87979EAFD54 Clave creada: mar 03 ago 2010 09:15:12 CLT La clave expira: jue 11 oct 2012 09:15:12 CLT Repositorio: Security tools (openSUSE_11.3) ¿Qué desea hacer, rechazar la clave, confiar temporalmente o confiar siempre? [r/t/s/?] (r): --------------------------------------------------------- Think a bit, do you believe that dialog is understanable for "joe user" ? If I was grandpa, I would be pretty scared..(and the same think is shown in Yast.btw) My suggestion are: a) make it *really* simple unless --verbose or some other advanced flags is passed , something like "Do you want to import key for $repository" ? ( Yes / NO) Defaults to YES, equivalent to "trust always" unless KEY is expired. 8-) Probably security people will excomulgate me, but users have not the slightless clue about what a GPG key or "temporary trust" is in this context, they just want to install packages..... b) make that dialog appear ONLY ONCE when there are multiple keys to be imported. <end of rant> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=647169 https://bugzilla.novell.com/show_bug.cgi?id=647169#c1 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low CC| |jkupec@novell.com --- Comment #1 from Ján Kupec <jkupec@novell.com> 2010-10-18 07:49:46 UTC --- Hi Christian! We will need to come up with some better improvement IMHO. b) is IMO totally unacceptable. a) maybe - if we provide an option for those who know about gpg signing to view the key information (ID, fingerprint) so that they can check the key. Frankly, i would close as WONTFIX. Zypper is not for "joe user" - YaST is. But i'll leave this open to get more opinions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=647169 https://bugzilla.novell.com/show_bug.cgi?id=647169#c2 --- Comment #2 from Cristian Rodríguez <crrodriguez@novell.com> 2010-10-22 11:49:41 CLST --- (In reply to comment #1)
Hi Christian! We will need to come up with some better improvement IMHO. b) is IMO totally unacceptable.
Why ? what's wrong with something like We have $N keys to import for: foreach ($repo..) echo "$repo ..." endforeach Would you like to Import all, check one by one, or none ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=647169 https://bugzilla.novell.com/show_bug.cgi?id=647169#c3 Bernhard Wiedemann <bwiedemann@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@novell.com --- Comment #3 from Bernhard Wiedemann <bwiedemann@novell.com> 2010-12-04 19:18:42 CET --- The yast2 UI also pops up one warning for each repo, where I would want a "trust all" function. yast2 has some extra explanation text about what this is, but not enough information on how to decide if fingerprint 0x12345678 could be trusted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com