Skip to content

Client 1.0.0 EA 3

Latest
Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 01 Jul 14:40
· 370 commits to master since this release
1.0.0-EA+3
dc47a40

Binaries

If you are looking for easy install on your Raspberry Pi, scroll down to "Install on Raspberry Pi"

Do not use Stream-Pi in public, open or untrusted networks. Always use this within your private and trusted networks. Stream-Pi does not use any encryption as of this version (1.0.0 EA+3)

Install on Raspberry Pi

If you have a Raspberry Pi System, you may run the following command via terminal or SSH:

Note: Raspberry Pi OS 32-bit recommended for the below method.

curl -sSL https://install.stream-pi.com/client/raspberry-pi | bash

This will install and configure the latest stable version (1.0.0 EA+3) on your Raspberry Pi, using this script.

After installation, you may run Stream-Pi Client using

  • Desktop Mode (For best compatibility): A shortcut is already created in your desktop, or you can also run ~/stream-pi-client/run_desktop in your terminal.
  • Console Mode (For best performance): Run ~/stream-pi-client/run_console in your terminal. Not supported on ARMv6 systems like Raspberry Pi 0 and 1.

Stream-Pi in Desktop Mode will not work while the Raspberry Pi is in Console Mode and vice versa.

Note for Other ARM 32 Systems

Extract the zip for ARM32, then run either run_console or run_desktop executable file inside the extracted folder.

  • If your ARM system has proper support for DRM/KMS, run run_console. Make sure X server is not running.
  • For best compatibility, run run_desktop executable. This requires X Server, and uses Software rendering.

Note for Android

  • Only 64-Bit Android devices are supported.
  • Only Android 5.0+ is supported.

Note for Linux x64

If youre downloading the zip, you will need to extract and then run Stream-Pi Server executable in the bin directory.

Note for Windows

You may get the SmartScreen alert while running the Installer. This binary is completely safe, and this alert is triggered because we are not a known publisher. If you're paranoid about your safety, you may compile and build Stream-Pi from source.

You will also have to provide firewall access to it to your network when you get the firewall prompt.

New Additions

  • Support for MacOS
  • Installers
  • Toggle Actions
  • Twitch Actions
  • Screen saver
  • Lots of other actions

Improvements

  • OBS - Possible toggle-able actions have been converted to toggle actions
  • Better and more efficient Communication System
  • Same action may now support multiple icons
  • Flat action box instead of rounded
  • Better run at boot support
  • Lots of other improvements

Known issues

  • Start at boot is not supported on MacOS. *
  • Console mode does not work on ARMv6 systems like Raspberry Pi 0 and 1. *

* Fixed and will not be present in next release.

Verify Authenticity

We provide signatures of the appropriate executable files that the users can use to verify whether these builds. In order to verify, do the following:

  1. Import GPG key

    gpg --keyserver keys.openpgp.org --recv-key D8A4A719A777D3AE19382A2C4F6C91BE7547DFFD

  2. Download the signature .sig file for the appropriate build you have downloaded.

  3. Verify

    gpg --verify <signature file> <executable file>

    Example:

    gpg --verify stream-pi-client-linux-x64-1.0.0-EA+3-executable.zip.sig stream-pi-client-linux-x64-1.0.0-EA+3-executable.zip

    If you get an output like the following:

     gpg: Signature made Thursday 24 February 2022 12:04:37 PM IST
 gpg:                using RSA key D8A4A719A777D3AE19382A2C4F6C91BE7547DFFD
 gpg: Good signature from "Debayan 'rnayabed' Sutradhar (Stream-Pi) " [ultimate]

    This means that the build is 100% genuine and has not been manipulated.

    However, if you get an output like the following:

     gpg: Signature made Thursday 24 February 2022 12:04:10 PM IST
 gpg:                using RSA key D8A4A719A777D3AE19382A2C4F6C91BE7547DFFD
 gpg: BAD signature from "Debayan 'rnayabed' Sutradhar (Stream-Pi) " [ultimate]

    This means that the build is NOT genuine, and you should immediately report it to us and refrain from using it.

Note

  • You may get a warning that the signatured is not trusted like the following:

    gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: D8A4 A719 A777 D3AE 1938  2A2C 4F6C 91BE 7547 DFFD

    This is expected and perfectly normal.

    If you have imported the exact key with fingerprint D8A4 A719 A777 D3AE 1938 2A2C 4F6C 91BE 7547 DFFD with E-Mail ID debayansutradhar3@gmail.com from keys.openpgp.org, you can be assured that this is the exact safe key, and can manually ask gpg to trust it by running

    gpg --edit-key D8A4A719A777D3AE19382A2C4F6C91BE7547DFFD
trust
<your desired option>
quit

    Other than that, gpg uses the "Web Of Trust" method to make sure that the keys you have imported are trustable. However, newer versions no longer import trust signatures by default and this article properly explains why it happened. Since keys.openpgp.org requires E-Mail verification, it does not require trust.

  • Verifying a build with the signature for another build will also cause a mismatch and return BAD signature. Make sure you use the appropriate signature for the respective build. For example, only use the signature file stream-pi-client-linux-x64-1.0.0-EA+3-executable.zip.sig for the build stream-pi-client-linux-x64-1.0.0-EA+3-executable.zip

Assets 16
Loading