[Bug 1278387] Re: Private key generation does not work at all

2014-02-11 Thread itzeme
Yes this is a upstream issue. However the seahorse project seems barely active, so if you want to have a working version of seahorse in the next Ubuntu release, you (Ubuntu developer) will need to fix some of those bugs yourself. -- You received this bug notification because you are a member of

[Bug 1278386] Re: seahorse can only generate pgp keys up to 4096 bit

2014-02-11 Thread itzeme
Yes this is a upstream issue. However the seahorse project seems barely active, so if you want to have a working version of seahorse in the next Ubuntu release, you (Ubuntu developer) will need to fix some of those bugs yourself. -- You received this bug notification because you are a member of

[Bug 1278386] Re: seahorse can only generate pgp keys up to 4096 bit

2014-02-11 Thread itzeme
Correction: since this is rather a functionality request my former post is not correct. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1278386 Title: seahorse can only generate

[Bug 1278381] [NEW] pgp key generation window not present

2014-02-10 Thread itzeme
Public bug reported: In the current version (today) of ubuntu 14.04: seahorse does not show a key generation window when creating a new pgp key, therefore giving no feedback at all about key generation. There also should be a process indicator showing how much of the can has been generated, as

[Bug 1278386] [NEW] seahorse can only generate pgp keys up to 4096 bit

2014-02-10 Thread itzeme
Public bug reported: The current version of seahorse in Ubuntu 14.04 does not show an option to generate pgp keys larger then 4096 bit. This should be raised to allow key sizes up to 8192 (at least) as is the case when generating ssh keys ** Affects: seahorse (Ubuntu) Importance:

[Bug 1278387] [NEW] Private key generation does not work at all

2014-02-10 Thread itzeme
Public bug reported: The current version of seahorse in Ubuntu 14.04 shows an option to generate a private key. It is neither obvious what kind of key this is nor does the option work at all, leaving fields for key type empty and not offering the possibility to active the Create button, leaving

[Bug 1278390] [NEW] diagnostic tab lock button

2014-02-10 Thread itzeme
Public bug reported: On Ubuntu 14.04 the tab privacy and security show a lock button that does not have any function anymore. Clicking the button does not have any effect at all, neither locking nor unlocking the setting for sending error reports and stuff. ** Affects: gnome-control-center

[Bug 1278392] [NEW] multiple option settings for lock screen

2014-02-10 Thread itzeme
Public bug reported: The option to set the time bevore activating screen lock is abviable to be set in the tab privacy and security as well als in brightness lock leving an inconsistent interface also in Security and Pivacy the time options to determin when to lock the sceen after it turned

[Bug 1257939] Re: Does not show fingerprint in key import dialog

2013-12-05 Thread itzeme
Perhaps 'fingerprint=on' isn't an option on all keyservers? Or perhaps they are using a more meager search mechanism that doesn't expose this information cheaply. The fingerprint was not shown using several different servers. It might be a simple bug like the key ID Variable used where the

[Bug 1257939] Re: Does not show fingerprint in key import dialog

2013-12-05 Thread itzeme
https://bugzilla.gnome.org/show_bug.cgi?id=719872 ** Bug watch added: GNOME Bug Tracker #719872 https://bugzilla.gnome.org/show_bug.cgi?id=719872 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu.

[Bug 1257939] [NEW] Does not show fingerprint in key import dialog

2013-12-04 Thread itzeme
*** This bug is a security vulnerability *** Public security bug reported: Using the seahorse option to find and import remote public keys, the properties dialog does not show the correct fingerprint but the key ID instead. to reproduce: go to remote, find remote keys, enter a valid search