Update README and configuration to replace RSA with Ed25519 for federation security

README.md

@@ -19,7 +19,7 @@ A modern, self-hosted BigBlueButton frontend with beautiful themes, federation,
 - ✉️ **Email Verification** – Optional SMTP-based email verification for user registration
 - 👤 **User Profiles** – Customizable avatars, themes, and language preferences
 - 📱 **Responsive Design** – Works seamlessly on mobile, tablet, and desktop
-- 🌐 **Federation** – Invite users from remote Redlight instances via RSA-signed messages
+- 🌐 **Federation** – Invite users from remote Redlight instances via Ed25519-signed messages
 - 🐉 **DragonflyDB / Redis** – JWT blacklisting for secure token revocation on logout
 
 ### Admin Features
@@ -376,7 +376,7 @@ Federation allows users on different Redlight instances to invite each other int
 ### Setup
 
 1. Set `FEDERATION_DOMAIN=your-domain.com` in `.env`.
-2. On first start, an RSA 2048-bit key pair is generated automatically and stored in `server/config/federation_key.pem`.
+2. On first start, an Ed25519 key pair is generated automatically and stored in `server/config/federation_key.pem`.
 3. Other instances discover your public key via `GET /.well-known/redlight`.
 
 ### How it works
@@ -384,7 +384,7 @@ Federation allows users on different Redlight instances to invite each other int
 1. **User A** on `instance-a.com` sends an invite to `userB@instance-b.com`.
 2. Redlight looks up `instance-b.com/.well-known/redlight` to discover the federation API.
 3. The invite payload is signed with instance A's private key and POSTed to instance B's `/api/federation/receive`.
-4. Instance B verifies the RSA signature against instance A's public key.
+4. Instance B verifies the Ed25519 signature against instance A's public key.
 5. **User B** sees the invitation and can accept or decline. Accepting provides a join link to the remote room.
 
 ---