Bug 266039 - add, edit, delete features for secure store entries via preference UI
Summary: add, edit, delete features for secure store entries via preference UI
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Security (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Security Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 266033 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-24 16:55 EST by Christian Luehe CLA
Modified: 2019-09-06 16:10 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Luehe CLA 2009-02-24 16:55:15 EST 
At the secure storage preference "content" page it is currently not possible
to add, edit and delete secure store entries. (It is possible only with debug option on.)

The UI shall provide features to modify the secure storage content to the end user:
- add new nodes
- add new entries
- edit nodes
- edit entries
- delete nodes
- delete entries
Comment 1 Christian Luehe CLA 2009-02-24 16:58:35 EST 
this is a more general request to "individual removal of secure store entries via preference UI" (https://bugs.eclipse.org/bugs/show_bug.cgi?id=266033)
Comment 2 Oleg Besedin CLA 2009-03-02 14:09:07 EST 
*** Bug 266033 has been marked as a duplicate of this bug. ***
Comment 3 Oleg Besedin CLA 2009-03-02 14:17:42 EST 
For the edit, one concern that people expressed is a situation when a passer-by could click a few buttons and see the password.

I guess one way to approach this would be to say that editing is guarded by a special "access" password created when the secure storage is created. As a possibility: when a new secure storage is created, a user is asked if: 1) They want it to be editable; 2) They want to have an explicit password to guard the edit functionality; 3) [paranoid option] If they want to make this explicit password cleared after every edit or kept for the duration of the session.

(If answer to (2) is no, then secure storage would generate the access password itself and keep it encrypted with the master password. This way editing will be possible only when user is logged in.)
Comment 4 Oleg Besedin CLA 2009-03-02 14:21:28 EST 
As a starting point, some of this functionality is available in debug mode added via org.eclipse.equinox.internal.security.ui.storage.view.NodesView#makeActions().
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:10:27 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.