After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 577710 - Cannot copy new WEP key over existing key
Cannot copy new WEP key over existing key
Status: RESOLVED DUPLICATE of bug 573689
Product: seahorse
Classification: Applications
Component: general
2.24.x
Other All
: Normal minor
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-04-02 12:27 UTC by Stephen Gallagher
Modified: 2009-10-15 00:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Stephen Gallagher 2009-04-02 12:27:40 UTC 
Open Seahorse and select the Passwords tab.
Double-click Network secret for <ssid>/wep-key0
Expand "Password:"

Copy a new WEP key to the clipboard from some other program. Attempt to paste it into the "Password:" field.

Neither ctrl-v/shift-ins, nor X middle-mouse paste will add data to this field, but one can manually type into it.

It would be far more convenient to be able to paste into this field than it is to manually type out a 128-bit HEX key.

Other information:
Comment 1 Adam Schreiber 2009-10-14 01:04:10 UTC 

*** This bug has been marked as a duplicate of bug 573689 ***
Comment 2 Stephen Gallagher 2009-10-14 11:19:08 UTC 
I contest that this is a duplicate of bug 573689.

That bug refers to copying the WEP key FROM Seahorse (to be pasted elsewhere). I can understand the reasoning behind disallowing that.

This bug is in regards to pasting IN a WEP key to Seahorse that is already in your clipboard.
Comment 3 Adam Schreiber 2009-10-15 00:34:08 UTC 
I'm choosing to fix these three bugs (see the other dup) by making sure you can cut and paste into the password field.  If you can paste into it, there's no further risk by being able to copy out of it.
Comment 4 Stef Walter 2009-10-15 00:52:50 UTC 
GTK 2.18 now has a GtkEntryModel for its GtkEntry in the latest version. If we can depend on that we can drop our own secure entry thing. This will fix problems with accessibility too.

I'll be working on this for gnome-keyring once we branch for gnome-2-28. I imagine the code would be very similar for seahorse.
Comment 5 Adam Schreiber 2009-10-15 00:56:34 UTC 
That's what I was thinking about.