Moving the community git server

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Moving the community git server
Date: 2011-07-05 21:35:59
Message-ID: CABUevEw+1X9uHE4HDVgbGKxgN3qWYbZv_3AQU=sHc8FUV=5u8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sometime later this week, the community git server
(git.postgresql.org) will be migrated to a new server in the same
datacenter. This does *not* affect the master git server for the
project, just the anonymous mirror and those that run standalone
projects on it, such as pgAdmin.

When this move is done, the IP will change to a different address in
the same subnet, and the server will have a new SSH key. That means
you will get a security warning if you use the ssh protocol. The
fingerprint of the new server is going to be:
cc:0c:27:40:d7:a2:98:f4:69:07:0c:b6:3a:05:19:71 - verify that this is
the one when you get a warning.

When the server has been migrated, the old one will be switched to
read-only access through http and git protocols for a day or two. The
ssh protocol will be completely turned off on the old server. If you
get an error about ssh login, it may simply mean that your DNS hasn't
yet updated.

I'll post again here with more details when the actual move happens,
but I wanted to get a notice out early since it will cause security
warnings for anybody trying to access it after the move.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2011-07-05 21:56:33 Re: Changing extension schema fails silently
Previous Message Peter Geoghegan 2011-07-05 21:31:35 Re: Changing extension schema fails silently