| Summary: | [other] keyring is not secure enough | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Genady Beryozkin <eclipse> |
| Component: | Runtime | Assignee: | platform-runtime-inbox <platform-runtime-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | fg, richard.birenheide |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
| Bug Depends on: | 50006 | ||
| Bug Blocks: | |||
|
Description
Genady Beryozkin
also if the user on unix uses a password, it is visible in the process list. One more bad thing about it is that the keyring file is created like any other file, with permissions (0666 - umask). Because many users have umask 022, I consider this a really serious bug. Thanks to the simple structure of eclipse it took me less than half an hour to get my personal keyring displayed. That's too easy. FYI, the cvs plug-in no longer uses the cache without the user explicitly saying that they will cache using an unsecure mechanism. This will be in the next 3.0 I-build. *** Bug 68268 has been marked as a duplicate of this bug. *** There are no plans to improve the keyring support in Eclipse. If you have greater cryptographic requirements, we recommend looking at other packages such as java.security.KeyStore. CVS is the only known client of the Eclipse keyring, but it makes caching in the keyring optional and provides the caveat that this does not protect you from people with access to your workspace data location. Why a simple solution like what mozilla has, is complex to implement? |