|Re: [eclipse.org-committers] SSH Auth Bot and your account security|
Hi Denis I 'own' a HIPP, so by your reasoning I should lose SSH access.However I regularly use SSH access for P2 repo maintenance, searching and general directory cleaning.
I'm not clear that doing this with scripts would be at all productive and might even risk stupidities.
Interactively, I can 'practice' my scripts one line at a time. If I'm forced into batch, impatience may cause me to do too much.
Regards Ed Willink On 15/01/2016 16:45, Denis Roy wrote:
Greetings committers, A handful of you have SSH access to build.eclipse.org. You may have seen the SSH Auth Bot block shell access to you from an unknown location at some time. Today we've had our first instance of unauthorized access. Fortunately, the SSH Auth Bot blocked that access and prevented a potential disaster for our data and our computer systems. But more importantly: _The committer informed us immediately_ If your account is blessed with shell access, we appreciate your continued attention to the SSH Auth Bot warnings you may receive. Moving forward, we'll be removing shell access from those accounts who do not have a valid need for it. Basically, any project that owns a HIPP instance has no real need for a shell, as the HIPP instance can run shell scripts on your behalf. We'll also be adding access history to your account page on dev.eclipse.org, so you can audit and monitor your access to our servers. Once pure Git is deprecated  and Gerrit is used for all our repos, SSH access will be entirely eliminated for all users except a few that I can count on my left hand. Local SSH access is our #1 security liability at the moment. Thanks again for being a good Eclipse citizen. Denis  https://bugs.eclipse.org/bugs/show_bug.cgi?id=452549
Back to the top