Legal
SSH access policy
Version 1.1 · Effective 28 October 2026
The terminal in the portal is a root shell on your server, opened through Trustane. Your server’s SSH stays closed to the internet: only Trustane reaches it. This policy adds to the Terms and the Acceptable use policy.
1. Who may open it
The account owner, and Trustane support. Opening a session needs two-step sign-in on the owner’s login, then its password and a fresh code from the authenticator app; together they open sessions in that browser for 15 minutes. You are responsible for everything done in a session opened with your login. Every session opened, by you or by Trustane support, is emailed to the account owner.
2. Root means everything
A root shell can change, stop or delete anything on the server, including the dialer, its database and its recordings. Nothing in the terminal asks before it acts. Take a backup before a change you cannot undo.
3. Trustane-managed files
Trustane runs these on your server and relies on them to reach it, protect it and keep calls flowing. Do not change, move, delete or disable them, or stop the services that use them:
- Firewall: the live rules (nft table inet lockdown); /etc/nftables.conf; /etc/nftables.d/lockdown.nft; /usr/local/sbin/trustane-fw-lists and its timer; /etc/trustane-fw/lists.json.
- Sign-in gate: /var/www/trustane-gate; /etc/trustane-gate; /etc/apache2/sites-available/trustane-gate.conf, /etc/apache2/ports.conf; /usr/local/sbin/trustane-gate-allow.
- Carrier sync: /usr/local/sbin/trustane-carrier-sync and its timer; /etc/trustane-carrier-sync.
- SSH: /etc/ssh/sshd_config; /etc/ssh/sshd_config.d; Trustane's key in authorized_keys.
- SSL: /usr/local/sbin/trustane-cert.sh.
- Database settings: /etc/astguiclient.conf.
- Trustane's logins: VICIdial users 6666, apiuser, tr_loader.
- Asterisk: /etc/asterisk/manager.conf; /etc/asterisk/ari.conf; /etc/asterisk/http.conf.
- Trustane's jobs: Trustane's lines in root's crontab, check_mariadb.sh.
Changing them can lock you and Trustane out, stop calls, or open the server to the internet. Change the firewall, the carriers and Trustane’s logins from the portal instead; ask support for anything else.
4. Files that are yours to change
Trustane set these up when it built the server, and they are yours to change: your dialplan, your SIP settings and your scheduled jobs. Trustane watches them, so the session log names what changed:
- Dialplan: /etc/asterisk/extensions.conf.
- PJSIP: /etc/asterisk/pjsip.conf.
- SIP: /etc/asterisk/sip.conf.
- Cron: root's crontab, except Trustane's lines; /etc/cron.d.
VICIdial writes extensions-vicidial.conf, sip-vicidial.conf and pjsip-vicidial.conf from its own settings and replaces them when those change, so an edit made there by hand is lost: change those through VICIdial’s admin pages.
5. What Trustane checks
Before each session Trustane takes a fingerprint of every item in sections 3 and 4, and again when the session ends. If an item in section 3 differs, the account owner and Trustane are told by email, naming each item. If only items in section 4 differ, the account owner is told. Trustane’s own changes during a session, made from the portal, are not counted as the session’s. Nothing is put back automatically. A root shell can hide a change from any check it can see, so this is a safeguard, not proof: a check the server will not answer is reported to Trustane too.
6. Fixes are billed per task
If a change made in a terminal session, to any file, breaks the server or a Trustane service and you ask us to fix it, we tell you what the fix involves and what it costs before we start, and charge only once you agree. The fix is billed per task, from your balance. We never bill for a fault of ours, or for undoing a change Trustane made. Until a fault caused by a terminal change is fixed, the service level does not apply to it.
7. Recordings and the session log
Every session is recorded: everything the screen showed, as it showed it. A password typed at a prompt that does not show it is not on the screen and is not recorded. The account owner and Trustane can replay a recording for 30 days; then it is deleted. The session log (who, from which address, when, for how long, the files moved, and the check in section 5) is kept for 365 days.
8. Files
Files of up to 100 MB each can be uploaded to the server or downloaded from it during a session, one at a time. Each one is in the session log. An upload replaces a file of the same name.
9. Limits
A session closes after 15 minutes with no typing, and after 4 hours in all. At most 2 sessions are open on one server at a time. The account owner can end any session from the portal. Trustane may end a session, or turn the terminal off for an account, to protect the server, its calls or other customers.
10. Use
Everything the Acceptable use policy prohibits is prohibited from the terminal too, including using the server to scan, attack or reach systems you have no right to reach.