Search code, repositories, users, issues, pull requests...

By default, Beam identifies your session using your public key. So, if you are using the same SSH keys on both the sender and the receiver end, you do not need to use an explicit channel name. When the same key isn't available on both the machines, you can use a random channel name. You can do this using,

SSH connections cannot be load balanced or geo-routed. So, unless you explicitly use the host closest to you, you might notice low transfer rates. The public beam.ssh.camp server is hosted in Falkenstein, Germany on Hetzner.

Beam cannot support end-to-end encrypted buffers. While data is encrypted during transfer to and from the Beam host, it’s decrypted temporarily before being re-encrypted and forwarded. The host only holds a small buffer (typically 1 kB) of unencrypted data at any time and never stores the full stream. For extra security, you can encrypt your files or pipes before sending them through Beam.

Some programs or system configuration may cause output buffering, preventing data from being sent to the pipe and reaching the beam SSH connection until the source flushes its buffer. For example, Python buffers stdout output by default. To avoid this, run Python with python -u or set PYTHONUNBUFFERED=1.

Leave a Comment