Community
Participate
Working Groups
Remote accounts that require key fobs for login are currently not well supported: 1) Secure storage and automatic password entry are enabled by default, and secure storage currently must be used because of bug 485366. This is especially bad for key fobs because Eclipse may attempt to reuse old passcodes, which will fail and, worse, could cause user's accounts to be disabled after too many failed attempts. 2) It is unclear to new users how to create connections, since neither public key nor password-based seems correct. (The latter has a box for entering a permanent password, which is confusing.) I propose adding a third method of authentication for key fobs that has secure storage and automatic password entry disabled.
The org.eclipse.remote component of the Eclipse Ecosystem has a new home. It is now part of the Eclipse CDT project[1]. This change means a new Git repo[2], P2 site[3] and Bugzilla component. The org.eclipse.remote will continue to be delivered as part of the quarterly Simultaneous Release of Eclipse as well. If this bug is no longer relevant, please feel free to comment or close the bug. If you can confirm if this issues still occurs in the latest release please do let me know in a comment. [1] https://wiki.eclipse.org/CDT/User/NewIn106 [2] https://git.eclipse.org/c/cdt/org.eclipse.cdt.git (in the remote directory) [3] first CDT release will be 10.6 - P2 site will be https://download.eclipse.org/tools/cdt/releases/10.6/ (This comment was added to all relevant org.eclipse.remote bugs along with changing the Product/component pair to CDT/remote.)
