Skip to content

Releases: stream-pi/server

2.0.0-SNAPSHOT

01 Jul 08:02
@github-actions github-actions
2.0.0-SNAPSHOT
b0ee7eb
Compare
Choose a tag to compare
2.0.0-SNAPSHOT Pre-release
Pre-release

Build Number : 289
These are snapshot builds. Untested and not recommended for daily use.

Assets 13
Loading

Server 1.0.0 EA 3

01 Jul 14:35
@github-actions github-actions
1.0.0-EA+3
8519043
Compare
Choose a tag to compare
Server 1.0.0 EA 3 Latest
Latest

Binaries

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)

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
  • 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. *
  • Media Key Action is not supported on MacOS. *
  • Toggle Actions revert to OFF when entering or returning from a folder. *
  • Toggle Actions do not work with Combine Actions. *
  • Check for Updates Button is non functional.
  • Factory Reset does not work. *

* 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-server-linux-x64-1.0.0-EA+3-executable.zip.sig stream-pi-server-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

  • Sometimes, 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 [email protected] 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-server-linux-x64-1.0.0-EA+3-executable.zip.sig for the build stream-pi-server-linux-x64-1.0.0-EA+3-executable.zip

Assets 12
Loading