ZapbirdDocs

Security

How Zapbird protects your project and your phone.

#Connection

The server makes a new TLS certificate each time it starts. The QR code carries that certificate, and the phone trusts only it, so another computer on the Wi-Fi cannot pose as yours. The server accepts only local addresses.

#Pairing

The QR code and the link hold a secret. Anyone who has it can connect to your server until it expires, so do not post it.

  • It works for 24 hours (--qr-hours 1 to 24) and stops when you stop the server.
  • A new QR code (type p) ends the old one.
  • --single-use-qr makes it work once.
  • Typing an address instead of scanning shows a 6-digit code on the phone. Type that code in the terminal to allow it, or n to refuse.

#Your code

The phone gets compiled bytecode and your assets, such as images and fonts, not your source files, unless you turn on phone editing.

A project that holds server-side keys, such as a Stripe secret, AWS keys or a service role key, is refused before it is sent. --allow-secrets overrides that and is not advised.

#Phone editing

Off unless you start with --allow-phone-edit. It reaches only the Dart files in lib/.

#SDK downloads

The published SDK list is signed by the publisher, and a list whose signature does not check is not used. Every download is checked against its checksum, and every file in it against the hashes inside, before anything is installed.

#Reports

Output and errors your project prints are sent to your terminal, with keys, tokens and passwords hidden.

Was this doc helpful?

Zapbird sends no analytics. Read about security.

Flutter and the related logo are trademarks of Google LLC. Zapbird is not endorsed by or affiliated with Google LLC.

esc