| Summary: | Exception after closing a launched eclipse application | ||
|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Claudia Knobloch <cla.knobloch> |
| Component: | Remote Tools | Assignee: | Project Inbox <ptp-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cjashfor, g.watson, wainersm |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Claudia Knobloch
+1 I'm seeing this bug too. After an investigation I've finally figured out what is going on here. For MacOSX or Windows there are native implementations of Equinox PasswordProvider, respectively, org.eclipse.equinox.security.macosx and org.eclipse.equinox.security.win32. Because there are native provides on both MacOSX and Windows, the master password (used by equinox security storage to encrypt data) might be generated automatically without user notice. There isn't any native implementation of PasswordProvider for Linux. Therefore, the master password isn't generated automatically and you gonna see the error stacktrace posted here. Notice the security storage is still able to save any sensitive data but rather in non-encrypted fashion. The remediation, in Linux, is to set the master password manually (Window > Preferences > Security > Security Storage > Change Password) but beware eclipse is going to ask for the password everytime it is started. There is an effort going on to provide a Linux native implementation of PasswordProvider. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=234509 More details about secure storage mechnism here: http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fsecure_storage_architecture.htm Closing as this is not a PTP problem. |