Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Linux release #618

Closed
alfred-landrum opened this issue Apr 15, 2020 · 1 comment · Fixed by #684
Closed

Initial Linux release #618

alfred-landrum opened this issue Apr 15, 2020 · 1 comment · Fixed by #684
Assignees
Labels

Comments

@alfred-landrum
Copy link
Contributor

We want to provide installable Linux releases of Brim. Our CI already builds and executes Linux based tests (using Ubuntu & xfvb). We have user reports about desired distros in #586 (note the comments there about flatpak.org) and a few other in the public #brim slack channel.

We currently use the Electron update service for autoupdates:
https://www.electronjs.org/docs/tutorial/updates

which does not support autoupdates on Linux. It will be acceptable if we don't initially support auto-update on Linux, but the user shouldn't see any errors or warnings about auto-update not working.

We need to:

  • decide on the packaging format(s) that we want to provide.
  • add support for them in script/release as we do for other platforms
  • add a CI trigger that will generate the release artifact & upload it as for other platforms
  • add an icon and links to the Linux package(s) on the brimsecurity.com/download page.
@philrz
Copy link
Contributor

philrz commented Apr 30, 2020

Verified. I made .deb and .rpm release artifacts and installed them via double-click in the Files utilities of Ubuntu Desktop 18.04 and Fedora Workstation 31, respectively. Per the attached videos, in each I was able to drag a pcap into the app and open flows in Wireshark successfully.

Ubuntu.zip

Fedora.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants