[Bug 522368] [NEW] seahorse-tool reports Invalid Signature and wrong date for expired keys
Public bug reported: Binary package hint: seahorse-plugins When verifying a detached signature that GnuPG reports as good, but one that was signed with a key that has since expired, seahorse-tool reports that the signature is invalid. Example files for testing: http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.1.tar.gz http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.1.tar.gz.sig seahorse-tool --verify mediawiki-1.15.1.tar.gz.sig FILENAME: Invalid Signature, Signed by NAME em...@address.com expired on DATE (See attached screenshot of libnotify message) 1. The signature should be treated as good, but a note should mention that the key has expired. See the following message example that GPG gives. gpg --verify mediawiki-1.15.1.tar.gz.sig gpg: Signature made Mon 13 Jul 2009 11:11:00 AM PDT using DSA key ID E8A3FEC4 gpg: Good signature from Tim Starling tstarl...@wikimedia.org gpg: Note: This key has expired! Primary key fingerprint: D7D6 767D 135A 514B EB86 E9BA 7568 2B08 E8A3 FEC4 2. The date that seahorse-tool displays appears to be the signature date, and NOT the key expiration date (see screenshot). This is misleading. In the above example, the file was signed on Mon 13 Jul 2009 11:11:00 AM PDT, but the key used to generate the signature expired on 2009-07-23. They appear to be swapped. gpg --list-key E8A3FEC4 pub 1024D/E8A3FEC4 2008-07-23 [expired: 2009-07-23] uid Tim Starling tstarl...@wikimedia.org An appropriately proposed message might look like the following: FILENAME: Good Signature, Signed by NAME em...@address.com with Key ID XXX on SIGNATURE_DATE. Note: Key expired on KEY_EXPIRATION_DATE ** Affects: seahorse-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: seahorse -- seahorse-tool reports Invalid Signature and wrong date for expired keys https://bugs.launchpad.net/bugs/522368 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse-plugins in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 522368] Re: seahorse-tool reports Invalid Signature and wrong date for expired keys
** Attachment added: Screenshot of notification message http://launchpadlibrarian.net/39245841/Screenshot.png -- seahorse-tool reports Invalid Signature and wrong date for expired keys https://bugs.launchpad.net/bugs/522368 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse-plugins in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 455129] Re: The black screen remains after opening the laptop
Just to add to this thread, I ended up creating a Gnome keyboard shortcut (Ctrl+Super+P) which executes vbetool dpms on. When the screen in non-responsive, I use the key combination and it turns the power back on. vbetool needs root privileges, so I just used the setuid attribute so normal users can run it. sudo chmod +s /usr/sbin/vbetool -- The black screen remains after opening the laptop https://bugs.launchpad.net/bugs/455129 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 455129] Re: The black screen remains after opening the laptop
I too am having this problem with clean installations of 9.10 Karmic on two dell laptops. Both are running integrated Intel graphic cards. Power settings have been set to Blank Screen on lid close. The system is still running in the background, CTRL+ALT+F1 and F7 are working in the background, but do not turn the screen back on. The screen's power is just off and won'y come back on. I'm sure some of the many previous workarounds might have some success, such as using a script that calls the command vbetool dpms on. e.g. https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/49521/comments/22 If you have an SSH server running on this machine, you can probably just remote in from another computer and run that command. I've had this issue before but not since version 7.10 or so. Something has changed obviously. -- The black screen remains after opening the laptop https://bugs.launchpad.net/bugs/455129 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 181703] Re: Brasero does not recognize audio CD or blank CD-R
Stephen, burning a CD from a playlist in Rhythmbox did the trick for me as well. Now Brasero recognizes blank CD-R discs appropriately. This was a pretty lame and frustrating bug. Is this even being looked at, anyone? -- Brasero does not recognize audio CD or blank CD-R https://bugs.launchpad.net/bugs/181703 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187335] Re: Unlock button throws an error, doesn't authenticate
Folks... for those of you trying to remotely run applications and are not presented with the unlock option, Martin Pitt came up with the solution in another bug report. [1] System - Administration - Authorizations - org, freedesktop, systemtoolsbackends, Manage system configuration. Modify the Implicit Authorizations with the Edit button, and change the Anyone value to Admin Authentication. (Screenshot attached) I am now able to unlock tools managed by policy kit remotely (e.g. SSH forwarding, NX, etc). [1] https://bugs.launchpad.net/bugs/183673 ** Attachment added: Screenshot-Authorizations.png http://launchpadlibrarian.net/15760104/Screenshot-Authorizations.png -- Unlock button throws an error, doesn't authenticate https://bugs.launchpad.net/bugs/187335 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187335] Re: Unlock button throws an error, doesn't authenticate
Sorry folks... I misspoke. NoMachine does not work for me either. I'm still investigating. A cheesy workround until then is to ssh -XC localhost from the NoMachine session. -- Unlock button throws an error, doesn't authenticate https://bugs.launchpad.net/bugs/187335 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187335] Re: Unlock button throws an error, doesn't authenticate
Just ran into this bug. Clean installation of Ubuntu Desktop 8.04. Running users-admin from console works as expected. Running users-admin or sudo users-admin from remote connection (e.g. ssh X11 forwarding, NXClient, etc) does not allow administrative access to unlock the tool. The error given is: ** (users-admin:9673): CRITICAL **: Unable to lookup session information for process '9673' -- Unlock button throws an error, doesn't authenticate https://bugs.launchpad.net/bugs/187335 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
