Infrastructure/Subversion/2020 Changes: Difference between revisions
(Add heading) |
(Bunch of rewording) |
||
| Line 9: | Line 9: | ||
If you have commit access, to continue having access to the SVN repository, | If you have commit access, to continue having access to the SVN repository, | ||
you will need to [https://invent.kde.org/profile/keys | you will need to add your SSH keys on KDE's GitLab at [https://invent.kde.org/ invent.kde.org] | ||
even if you only use Subversion | ([https://invent.kde.org/profile/keys link to your GitLab SSH keys]), | ||
even if you only intend to use Subversion. | |||
In addition, if you're not in the [https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list list of users with SVN access], | |||
please [https://go.kde.org/systickets file a sysadmin ticket] and we'll add you. | please [https://go.kde.org/systickets file a sysadmin ticket] and we'll add you. | ||
Finally, the host | Finally, the SSH host keys of the server will necessarily change, | ||
and you will get a nasty warning about it | and you will get a nasty security warning about it. | ||
You should | You should remove the old host key from <tt>known_hosts</tt> as the warning explains, | ||
then make sure the new host key fingerprint matches one of these before accepting it: | |||
<!-- these are leptone's host key fingerprints --> | <!-- these are leptone's host key fingerprints --> | ||
<pre> | <pre> | ||
Revision as of 02:50, 16 April 2020
April 2020 changes to Subversion server
As part of KDE's migration to GitLab, we will be moving our Subversion repository to a new server. To simplify our systems, we will also move the management of SSH keys to GitLab, and we will begin limiting access to the Subversion repository only to those actively using it.
If you have commit access, to continue having access to the SVN repository, you will need to add your SSH keys on KDE's GitLab at invent.kde.org (link to your GitLab SSH keys), even if you only intend to use Subversion.
In addition, if you're not in the list of users with SVN access, please file a sysadmin ticket and we'll add you.
Finally, the SSH host keys of the server will necessarily change, and you will get a nasty security warning about it. You should remove the old host key from known_hosts as the warning explains, then make sure the new host key fingerprint matches one of these before accepting it:
2048 SHA256:rgF+nO+jdBEKOdowaOZBnaeWtAV6vquW4EjFafO1aaM (RSA) 256 SHA256:UutSIkXdSGgyxQxL35dDEEAD2Owel+zEdKZ5I/JMqrA (ECDSA) 256 SHA256:tPgR57xn3BJVri4ncIMAtj/3Dxc9SB/ijOxORUTCQFk (ED25519) 2048 MD5:32:c9:78:b1:1f:7c:2e:1c:12:26:62:1c:67:d0:6c:28 (RSA) 256 MD5:cb:56:a3:74:a8:69:5c:f3:93:b0:dc:f9:05:1c:3f:9a (ECDSA) 256 MD5:c8:99:54:39:84:9b:e5:39:1a:de:c6:6d:fa:4d:a4:e8 (ED25519)