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

Bug 540017

Summary:	Unable to ssh into dev.eclipse.org
Product:	Community	Reporter:	Roland Grunberg <rgrunber>
Component:	CommitterTools	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Roland Grunberg

2018-10-10 16:02:43 EDT

When attempting to connect :

OpenSSH_7.8p1, OpenSSL 1.1.0i-fips  14 Aug 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *
debug1: Connecting to dev.eclipse.org [198.41.30.200] port 22.
debug1: connect to address 198.41.30.200 port 22: Connection timed out
ssh: connect to host dev.eclipse.org port 22: Connection timed out

Is there some block in place ?

Comment 1 Eclipse Webmaster

2018-10-11 11:17:40 EDT

The timeout certainly implies a block.  If you login to https://accounts.eclipse.org it should pop a warning if the IP you logged in from is blocked.  If so, and you need it unblocked just send your IP to Webmaster and we'll look into it.

Just so you know we haven't supported ssh access to dev for a couple of years, and the limited access available via build is being phased out.

-M.

Comment 2 Roland Grunberg

2018-10-11 12:31:54 EDT

(In reply to Eclipse Webmaster from comment #1)
> The timeout certainly implies a block.  If you login to
> https://accounts.eclipse.org it should pop a warning if the IP you logged in
> from is blocked.  If so, and you need it unblocked just send your IP to
> Webmaster and we'll look into it.

I tried logging back into accounts.eclipse.org but I don't see any popup (no ad-block used) regarding my IP being blocked. I even tried from another laptop on the same network.

> Just so you know we haven't supported ssh access to dev for a couple of
> years, and the limited access available via build is being phased out.

I mainly used the existing ssh support to use some basic file operations on download.eclipse.org. I know that maintainers are encouraged to automate such work through the JIPPs but for basic things like moving certain files / modifying certain pages is there a recommended way to continue doing this ?

Comment 3 Roland Grunberg

2018-10-12 10:12:28 EDT

The issue seems to be resolved and I can authenticate over ssh. Feel free to close.

Comment 4 Eclipse Webmaster

2018-10-15 13:08:57 EDT

(In reply to Roland Grunberg from comment #2)

> I know that maintainers are encouraged to automate
> such work through the JIPPs but for basic things like moving certain files /
> modifying certain pages is there a recommended way to continue doing this ?

As you note automation via a JIPP is our recommended option.

-M.