পণ্যের অংশে চলে যান
LCPanelলাইসেন্স সেন্টার প্যানেল

নিরাপত্তা

HTTPS, পাসকোড ও ওয়েটিং রুম, ব্যান, টু-ফ্যাক্টর সাইন-ইন, রেট লিমিট, সার্ভার কী রক্ষা করে, রেকর্ডিং ও গোপনীয়তা, আর চেকলিস্ট।

ডেভেলপার, নিরাপত্তা ও সাহায্য হালনাগাদ ৬ নভে ২০২৬ ২৫ / ২৬

A meeting platform sees private conversations. This chapter shows what protects them and what you must do yourself.

1. HTTPS

Use HTTPS on the whole site. Browsers refuse the camera and microphone on plain HTTP, and sign-in cookies and passcodes must not travel in clear text. After AutoSSL or Let's Encrypt is on, redirect HTTP to HTTPS in your host panel. The Health and Security Check page warns when the site is not on HTTPS.

Media between browsers is encrypted by WebRTC (DTLS-SRTP). The server never sees the video in a mesh call. A TURN relay passes encrypted packets only.

2. Passcodes and the waiting room

  • Passcodes. A passcode is 6 characters by default and the host may set 16. Turn on "Every meeting needs a passcode" to force one. Rotate it with New passcode on the meeting page.
  • Passcode in the link. Convenient, but anyone with the link can enter. For sensitive meetings turn off "Put the passcode into the join link" and tell people the code another way.
  • Waiting room. Keep it on for public links and for the personal room.
  • Lock meeting. Close the door when everyone has arrived.
  • Guests. Switch off "Guests may join without an account" if only members should enter.
  • Hosts need a verified e-mail. Keep it on so throwaway accounts cannot start rooms.

3. Removing and banning

A host can remove a person. A removed person cannot rejoin the same session. Staff can ban an IP address or a whole e-mail domain under Users, Banned IPs and E-mail Domains. Banned addresses cannot sign in or register.

4. Account security

  • Two-factor sign-in (2FA). Members and staff can turn on an authenticator app under Account. They get recovery codes and can mark trusted devices. Staff accounts should always use 2FA. The Security settings can require it for staff.
  • Strong passwords. The password policy refuses weak passwords. Passwords are stored with the PHP password hashing function.
  • Sessions and devices. Members see their active sessions and devices and can sign out the others. Staff see all sessions under Users, Active Sessions and can end any.
  • Login history. Every attempt, good and bad, is logged with IP and device.
  • E-mail verification. Members confirm their address by a link.
  • Captcha. The registration, login and contact forms can use a captcha. Choose the type under Settings, Security.

5. Rate limits and brute-force protection

  • Sign-in. After 5 wrong attempts (setting login_max_attempts) the address is banned for 15 minutes (login_ban_minutes). A whitelist of trusted IPs can be set.
  • Meetings. A host may create 60 meetings per hour by default, so a stolen account cannot flood the system.
  • API. 120 calls per minute with a key, 30 per minute per IP without.
  • Forms. Registration, contact, search and join attempts are rate limited.

6. What the server protects

  • Every form has a CSRF token.
  • Security headers are sent: content type, frame, referrer and permissions policies.
  • Secrets such as TURN passwords and gateway keys are stored encrypted with the install secret.
  • Uploads go to folders that are not executable. Recordings are served through the site with access checks. Private recordings do not open for strangers.
  • Staff actions are written to the Admin Audit Trail with before and after values.
  • Security events (bans, failed sign-ins, suspicious requests) are listed under Reports, Security Events.
  • The meeting room page is noindex, so search engines never list rooms.

7. Recordings and privacy

Tell people when you record. The room shows a recording notice to everyone. Keep recordings private by default, and use a passcode on shared links. Set "Delete cloud recordings after (days)" to what your privacy policy promises. Put your retention rules in the Privacy page.

8. Your own checklist

  1. HTTPS on, and HTTP redirects to it.
  2. config.php, data/ and the backups are not readable from the web. The Health check tests this.
  3. 2FA on every staff account.
  4. Waiting room and passcode on by default.
  5. Cron running, so stale sessions end and tokens expire.
  6. Backups of the database and uploads/, kept off the server.
  7. PHP and the script updated. Run the database update after every update.
  8. A TURN server with a shared secret (not a fixed password) if you use TURN.
  9. Review Security Events weekly.

9. Reporting a problem

If you find a security problem in AIOMeeting itself, write to info@faruk.bd with the details. Please do not post it publicly before it is fixed.

এটি কি কাজে লেগেছে?
এই অধ্যায়টি শেয়ার করুন