Re: ACTION REQUIRED - Gitlab and Subversion server migration
On 2023-07-23 22:01, Ben Cooksley wrote: > Good morning KDE Developers, > > As many of you will be aware, today Gitlab and our Subversion repository > were both migrated to a new home - on a more modern and more powerful > server, which should better support future work. > > As a consequence the host key of the server has now changed, which means > you will need to take steps on your system otherwise you won't be allowed > to connect to the new server. Was it possible to transfer keys from the old server? > Please ensure you run the following two commands to clear out any existing > host keys: > - ssh-keygen -R invent.kde.org -f ~/.ssh/known_hosts > - ssh-keygen -R svn.kde.org ~/.ssh/known_hosts > > Following these commands the next time you try to connect you will be > prompted to confirm the new host key and trust it for use. For those who > would like to confirm that host key, it is as follows: > > 256 SHA256:zHdK2R/S6s5Oj71N0s8LHWCXXsUt+DCztd+GjzW9KlU root@lerwini > (ED25519) > 256 SHA256:ZNBg4AkRxbt/N6xzpt7GbmmS78A3WFy5lz0l/cPHbcE root@lerwini (ECDSA) > 3072 SHA256:KxAoV6VsbKvAocFZCJlxtmPDScmUCRNiUiOCSXNSC/k root@lerwini (RSA)
Mailing list for people involved in Linux distributions
Distro people! We're starting a mailing list for coordinating on cross-distro problems, "fire of the week", anything which needs - or would benefit from - distributions speaking to each other. Example topics include: * "new $X is totally broken oh god" * coordination of stuff like time_t migration * discussing how to handle something new (the github unstable-tarballs incident would be a good example) Please consider subscribing: distributi...@lists.linux.dev (link on lists.linux.dev / https://subspace.kernel.org/lists.linux.dev.html) Do join too if you're an upstream and interested in these topics, especially if you're writing core software. We want a diverse set of opinions and perspectives! Pass it on to other distribution folks / packagers too. Cheers!
Re: Gitlab update, 2FA now mandatory
On 2022-10-23 19:16, Jack wrote: > On 2022.10.23 02:32, Ben Cooksley wrote: > > As part of securing Invent against recently detected suspicious > > activity I > > have also enabled Mandatory 2FA, which Gitlab will ask you to > > configure > > next time you access it. This can be done using either a Webauthn > > token > > (such as a Yubikey) or TOTP (using the app of choice on your phone) > > > > Should you lose access to your 2FA device you can obtain a recovery > > token > > to log back in via SSH, see > > https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html#generate-new-recovery-codes-using-ssh > > for more details on this. > > > > Please let us know if there are any queries on the above. > > > > Thanks, > > Ben > Sorry to be dense, but without a webauthn token device, it seems I'm at > a total block if I don't have a phone (or don't have it with me.) Is > that correct, or is there some fine manual I need to read? You can generate TOTP codes using KeePassXC.
Re: is a BSL licensed service acceptable for sysadminy use cases?
> After 36 months, the code becomes Apache-2.0 licensed (the conversion period) So you can use old sentry versions, which are open source.
