Phone test client¶
A development aid: a phone acts as the receiver's camera, speaker and buttons while all protocol logic (decoding, keys, unpack) runs on the host. The phone never holds the key. It is a test tool, not part of the real path.
Install and run¶
pip install -e ".[mobile,audio]"
lightferry mobile-serve --path ./my-folder --key-file lightferry.key
The command prints a Phone URL, a screen URL (https://LAN_IP:PORT/screen?...), a QR code and the SHA-256 of a freshly generated self-signed certificate. Both URLs carry a random token.
- Open the Phone URL on the phone. Accept the certificate warning (compare the fingerprint if you want).
- Press Start, grant camera and audio access.
- Open the screen URL on the host and point the phone at it.
- Confirm the VERIFY code with the on-screen buttons: on the screen page (sender) and on the phone (receiver).
Options¶
| Flag | Meaning |
|---|---|
--path |
folder or file this machine sends; with --remote-sender, the destination directory |
--port |
default 8443 |
--host |
bind address, default this machine's LAN IP |
--backchannel |
audio (default): replies are note tokens played by the phone; direct: replies go straight to the sender, a test shortcut |
--remote-sender |
the sender is another machine running lightferry send --no-camera --backchannel audio; the phone scans that machine's screen |
--out DIR |
where received files go (default out/received) |
--key-file, --key |
key, as for other commands |
Notes¶
- Use a trusted network. The server binds the LAN IP only, not
0.0.0.0;--hostoverrides it. One WebSocket client at a time: a second gets HTTP 409. - A new self-signed cert is made per run in a private temp dir and removed once loaded.
python -m lightferry.mobile ...is the same aslightferry mobile-serve ....LIGHTFERRY_DEBUG=1prints per-frame debug lines; nothing is dumped to disk otherwise.- Browsers require HTTPS for camera access, hence the self-signed certificate.
- Needs the
mobileextra (aiohttp, segno, cryptography).