You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Have the actual binary ninja Python library installed
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:
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
The text was updated successfully, but these errors were encountered: