⚒Anvil
Sign in

clo / cl-site public

merged

added some news blurbs 110

opened by common-lisp.net

Dave Cooper (@dcooper) on GitLab, 2025-03-12.

2 commits, 1 file changed

Commits
CommitAuthorWhen
fixed malformed markdown 69816608Dave Cooper
fix typo b30c1d76Dave Cooper
Changes
content/news.mdmodifiedview

@@ -4,21 +4,10 @@
 
 # Latest Common-Lisp.net news
 
-### 2025-03-12
+### 2025-03-12 
 
-#### Accepted SSH Key Types
-In reference to the below "Possible Need to Update SSH Keys," here are
-the specifics:
-
-* RSA, ED25519, and ED25519-SK are all OK **if** they are new enough,
-  e.g. generated with a reasonably recent `ssh-keygen`.
-
-* ECDSA cannot be used, nor can any keypairs which are too old (even
-  of the type liste above).
-
-If in doubt please reach out. 
-
 #### New Toplevel Host IP Address
+
 The toplevel `common-lisp.net` domain (which you're presumably looking
 at right now) has been changed to point to our new host, the same as
 `gitlab.common-lisp.net` and `future.common-lisp.net`. Most ssh user
@@ -31,14 +20,15 @@
 accordingly to point to the legacy hostname.
 
 #### Possible Need to Update SSH Keys To Access New Host
+
 NOTE: The new host has stricter SSH key requirements than the old one,
 so for example older, weaker RSA keys may no longer work. We don't
 plan to enable support for legacy keys which are considered insecure
 by today's standards. If this appears to affect you, please generate a
-new keypair and send the public key to the clo-devel mailing list
-(which we assume you're already on if you had ssh access to the old
-host), or ask for support at the IRC channel noted in the previous
-News item.
+new keypair (RSA, ED25519) and send the public key to the clo-devel
+mailing list (which we assume you're already on if you had ssh access
+to the old host), or ask for support at the IRC channel noted in the
+previous News item.
 
 ### 2025-03-03
 
common-lisp.net mentioned in commit b58af09ab58690fedbbf2dc919e2b42e65099969

Sign in to comment.