Community
Participate
Working Groups
Build ID: Eclipse 3.5m4 With the new Proxy UI introduced in bug #228739, an "Eclipse" Proxy profile is automatically available. I have my Eclipse CVS Repositories configured to use :extssh:moberhuber@proxy.eclipse.org:443/cvsroot/eclipse which works fine with the "direct" proxy setting. But when I switch to the "Eclipse" Proxy profile (which I'd expect to work fine for proxied access to Eclipse.org), my CVS access no longer works. I notice that making the proxy change may require quit & restart of Eclipse to get visible. This may be related to bug 240270, and may be related to bug 106586. Workaround: Add an entry for "proxy.eclipse.org" into the "proxy bypass" table. It might make sense to have this entry auto-generated.
While I had previously tested the extssh method only, I noticed today that if the "Eclipse" Proxy provider is in place, a :pserver:dev.eclipse.org connection also fails with the following message in a dialog: Could not connect to :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse: I/O exception occurred: ProxySOCKS5: com.jcraft.jsch.JSchException: fail in SOCKS5 proxy ProxySOCKS5: com.jcraft.jsch.JSchException: fail in SOCKS5 proxy I thus changed the summary, previous value was: [Proxy] CVS extssh connection fails with the "Eclipse" Proxy profile
Adding ymnk to comment on the JSch SOCKS error message
(In reply to comment #1) > While I had previously tested the extssh method only, I noticed today that if > the "Eclipse" Proxy provider is in place, a :pserver:dev.eclipse.org connection > also fails with the following message in a dialog: > > Could not connect to :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse: I/O > exception occurred: ProxySOCKS5: com.jcraft.jsch.JSchException: fail in SOCKS5 > proxy > ProxySOCKS5: com.jcraft.jsch.JSchException: fail in SOCKS5 proxy This message means that the socket connection has been successfully established, but the remote is not the socks5 server. I'm sorry, but it is not clear for me what is your problem. Did you intend to use socks5 proxy, but it did not be functional? Or, was the socks5 proxy unexpectedly enabled?
My problem is: I have no idea how proxies work and what capabilities are needed. I'm an end user in this respect. I have troubles accessing the Eclipse services, so I'm thinking that I should probably set up a proxy (since I have read this somewhere). In fact, under General>Network Preferences, I find a Proxy Preference page, and WHOA! there is a predefined "Eclipse" Proxy profile. Seems like to solve my problem, so I pick it. But, it does not solve my problem, it leads to more problems. Looks like either the "Eclipse" Proxy Profile is not well-defined (because there is no proper SOCKS5 proxy, I don't know?), or some code is broken somewhere. For instance, if I want to use CVS extssh through proxy.eclipse.org, I need to change all Repository entries from "dev.eclipse.org:22" into "proxy.eclipse.org:443". Is this expected? Is this the way we want it to be, given that there is now an "Eclipse" Proxy Profile?
(In reply to comment #4) > In fact, under General>Network Preferences, I find a Proxy > Preference page, and WHOA! there is a predefined "Eclipse" Proxy profile. Seems > like to solve my problem, so I pick it. > "Eclipse" profile means that you define those settings in the Eclipse via preference page (vs. in OS). I realize now that it is not the most fortunate name. Maybe it should be changed to "Manual". What do you think?
Created attachment 124957 [details] Patch_v01 Patch that changes "Eclipse" provider name to "Manual".
"Manual" is definitely a better name since products built on Eclipse can be branded with totally different names.
(In reply to comment #7) > "Manual" is definitely a better name since products built on Eclipse can be > branded with totally different names. > So, would patch from comment 6 solve your problem? Or have you got additional issues with the "Eclipse" proxy provider?
(In reply to comment #6) > Patch that changes "Eclipse" provider name to "Manual". Released to HEAD, but leaving bug open.
Closing the bug as FIXED. However I'm not sure if patch from comment 6 solves it completely. If some other problems still occur with "Manual" proxy provider (former "Eclipse") please reopen.
