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

CI Runner for Binary Ninja (and others) #42

Open
mahaloz opened this issue Mar 30, 2024 · 0 comments
Open

CI Runner for Binary Ninja (and others) #42

mahaloz opened this issue Mar 30, 2024 · 0 comments
Labels
binja enhancement New feature or request

Comments

@mahaloz
Copy link
Member

mahaloz commented Mar 30, 2024

Problem

We often find small bugs in decompilers that could've been found through a CI. Unfortunately, Binary Ninja, and others, is a paid decompiler which requires us to have a private CI to:

  1. Have the actual binary ninja Python library installed
  2. Have our license to use that library

If we had a CI, we could've caught:
binsync/binsync#355

Solution

Option 1

Figure out how private runners work, make a private CI in the SEFCOM Lab and connect it to BinSync GitHub

Option 2

Ask the Binja people to make a binary accessible through GitHub actions but only usable if you have a license. Make the license a secret token.

Still thinking up solutions

@mahaloz mahaloz added enhancement New feature or request binja labels Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binja enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant