Option to download *_sources.json from an external source

[MexHigh]

Is there a way to pull in a *_sources.json from an external source without rebuilding Forge? Usually, it is needed to add something like this to the collection_sources.json file:

[
    // other entries ...
    {
        "name": "MyCustomCollection",
        "type": "bof"
    }
]

which would load MyCustomCollection_sources.json from disk, where all the supported BOFs are listed. Is there a way to store this in a remote location instead, so that updates to MyCustomCollection would be visible in the running Mythic instance?

If not, consider this to be a feature request :)

[its-a-feature]

If you update the *_sources.json file I don't think you'll need to rebuild. Depending on what you change, you should just need to restart that container.

I don't have a way to remotely fetch those files though 🤔 if i'm understanding correctly, you want a way to indicate to the forge container that instead of reading these files from disk, that it should first fetch them from some specified URL? What about for all the associated bof / extension files?

[MexHigh]

if i'm understanding correctly, you want a way to indicate to the forge container that instead of reading these files from disk, that it should first fetch them from some specified URL?

Yes. The use case is that I have some Mythic instances and a curated *_sources.json file. I want to have a way to keep the Mythic instances up to date with a centralized BOF list, without having to setup some weird crontab stuff manually on all servers.

What about for all the associated bof / extension files?

Aren't they downloaded upon registration of the command? I think it would be fine to just not update registered commands automatically within an instance. Instead, if you want to update it, a "reregister" would be required. This way, running operations are not disrupted.

[its-a-feature]

If the forge container fetched down a remote *_sources.json file locally to parse and register, what are your thoughts on how it would know when to re-fetch for updates?

[MexHigh]

I think periodically (once per hour, maybe) and manually would be sufficient to begin with. A separate command like forge-update -collectionName <my-collection> would be useful.

[its-a-feature]

hmm i'm hesitant to add something into the agent that would automatically try to reach out periodically like that since there are people that deploy on hosts without internet access. That said, a separate update command I can see. Then, you could use Mythic's eventing to kick off that command on your own cron interval

[MexHigh]

Good point. I have never used the eventing feature before, but if you say that you can accomplish periodic command execution with it, then this is perfectly fine for me.