Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 235811

Summary:	Cannot connect to cvs using ssh
Product:	Community	Reporter:	Anthony Berent <aberent>
Component:	CVS	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	anne.jacko, chris.marshall, sharon.corbett
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Anthony Berent

2008-06-05 09:00:58 EDT

Some time in the last few days our site (ARM Ltd., Cambridge) have lost ssh access to dev.eclipse.org and proxy.eclipse.org. As a committer I need this access to allow me to check in my final bug fixes for Ganymede. 

According to whatsmyip.org my IP address is 217.140.96.21.

- Anthony

P.S. This may duplicate an email sent by our Information Systems department.

Comment 1 Denis Roy

2008-06-05 09:12:16 EDT

Your IP address must have changed recently, because the entire 217.140.0.0 subnet has been blocked on our firewall since November 2007 because of multiple SSH attacks against our servers.

I've requested 217.140. be removed from the block.  We'll define more precise rules for the 217.140. subnets that attacked us, as yours is not one of them.

Comment 2 Chris Marshall

2008-06-05 09:24:17 EDT

Denis, 

Thanks for your prompt response and confirmation that our /20 wasn't one that made any attacks (not that I expected that it would have done).

However, I'm sill a bit confused because the IP addresses our various sites use to break out to the Internet haven't changed since sometime in the second half of 2007.  Most haven't changed for longer than that. 

Regards,

--Chris

Comment 3 Anthony Berent

2008-06-05 09:36:08 EDT

Is the blocking of the proxy (port 443) new? I think it was about last November that I discovered that I could no longer use dev.eclipse.org, but could use proxy.eclipse.org in its place (as described on http://wiki.eclipse.org/index.php/CVS_Howto). At that time I did not investigate further, but simply used the workaround I had. The proxy only stopped working sometime between Monday and today.

- Anthony

Comment 4 Denis Roy

2008-06-05 09:45:48 EDT

(In reply to comment #3)
> Is the blocking of the proxy (port 443)

Ah that explains it. The block only affected SSH (port 22).  proxy was unaffected;  however, proxy died about 7 hours ago, and we're working on fixing.

We'll work towards removing the SSH block so that you can work with SSH instead of going through proxy.  I believe that proxy is back online as I type this, so you should be okay, but I recommend switching to SSH once it's available to you.

Comment 5 Anthony Berent

2008-06-05 09:47:08 EDT

Thanks,

Now working.

- Anthony

Comment 6 Eclipse Webmaster

2008-06-05 13:43:57 EDT

Closing as fixed.

-M.