overview

A Python CLI that logs you into the Sophos web auth portal used at JIIT hostel and LRC, then keeps the session alive. Credentials sit in SQLite. If one ID hits a data cap or fails, the script tries the next one.

tashifkhan/sophos-auto-login · tashifkhan/sophos-auto-login

Older docs lived at sophos-autologin.tashif.codes.

• Overview
• Quick start
• Command-line usage
• Interactive menu
• Daemon mode
• Advanced features
• Setup guide
• Screenshots

autologin.py is the entry point. It talks to http://172.16.68.6:8090/httpclient.html with form fields the portal already understands:

• Login uses mode=191 plus username and password.
• Logout uses mode=193 on the same URL.

The portal answers with XML. module.login reads the <message> text. A successful sign-in looks like You are signed in as {username}. Two failures make it skip to the next stored ID:

• Login failed. You have reached the maximum login limit.
• Your data transfer has been exceeded, Please contact the administrator

After a successful login, login() sleeps two minutes, then optionally runs a speed test. The outer loop in run_auto_login() is what keeps you online after that. It checks connectivity every 90 seconds (CONNECTION_CHECK_INTERVAL). If you are offline, it logs in again. Even if you look online, it forces a re-login every 30 minutes (FORCED_RELOGIN_INTERVAL) so the portal does not expire the session.

The README’s “every 2 minutes” line is that sleep inside login(), not the keep-alive loop.

CLI and menu both go through CredentialManger for storage and through module.login / module.logout for the portal. Active ID lives in module.state.

flowchart LR
  User["You"]
  CLI["autologin.py"]
  UI["ui.console Rich TUI"]
  CM["db.CredentialManger"]
  DB["SQLite credentials table"]
  Login["module.login"]
  Logout["module.logout"]
  State["module.state"]
  Portal["Sophos portal\n172.16.68.6:8090/httpclient.html"]
  Net["module.check_internet_connection"]

  User --> CLI
  CLI --> UI
  CLI --> CM
  CM --> DB
  CLI --> Login
  CLI --> Logout
  Login --> Portal
  Logout --> Portal
  Login --> State
  Login --> Net
  CLI --> Net

flowchart TD
  Start["run_auto_login"]
  Load["credential_manager.get_credentials"]
  Empty{Any IDs?}
  First["module.login walks the list"]
  Sleep["sleep 10s"]
  Tick{"90s since last check?"}
  Http["GET google.com or cloudflare.com"]
  Up{Internet up?}
  Age{"30 min since last login?"}
  Again["module.login again"]
  Stop{login returned stop?}
  Out["logout active ID and exit"]

  Start --> Load --> Empty
  Empty -->|no| Out
  Empty -->|yes| First --> Sleep --> Tick
  Tick -->|no| Sleep
  Tick -->|yes| Http --> Up
  Up -->|yes| Age
  Age -->|no| Sleep
  Age -->|yes| Again
  Up -->|no| Again
  Again --> Stop
  Stop -->|yes| Out
  Stop -->|no| Sleep

Created on first run:

CREATE TABLE IF NOT EXISTS credentials (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  username TEXT UNIQUE NOT NULL,
  password TEXT NOT NULL
);

On Unix the live file is ~/.autologin_script/credentials.db. On Windows it is %APPDATA%\autologin_script\credentials.db. If that file is missing and a bundled credentials.db sits next to the script or frozen binary, the manager copies it over.

Daemon logs are a different directory: ~/.sophos-autologin/.

• SQLite storage with unique usernames.
• Walk the credential list when one ID is at its login or data limit.
• Flags for start, add, edit, delete, import, export, show, daemon, exit, logout, speedtest, status.
• Interactive menu when you pass no flags.
• CSV in and out, including old UserID (Enrolment Number) headers.
• Unix daemon via double fork. Needs --start.
• Connection check every 90 seconds.
• Forced re-login every 30 minutes.
• Desktop notifications on login, logout, and daemon events.
• Speed test after a successful login, and on demand from the menu or --speedtest.