Keep all releases to allow installation in CommandoVM & FLARE-VM

[Ana06]

We provide a package for MemProcFS in VM-Packages, making it available for CommandoVM and FLARE-VM. Normally tools that use GitHub releases do not change the assets after the release and keep all released minor versions. But MemProcFS seems to change the assets of the release updating the date in the name. This causes that the URL used in our package breaks and we are not able to install the tool. Our community really likes MemProcFS and they have tried to update the URL and hash in the package in the following PRs, but a new release have broken them:

• Fixed and updated memprocfs.vm to latest version mandiant/VM-Packages#1411 (2 weeks old)
• fixed dead link of memprocfs and updated hash mandiant/VM-Packages#1420 (1 week old)

We could use v5.13.4 as the assets v5.13.4-win_x64-20241229.zip doesn't seem to change anymore. But this is not ideal, as our community would like to use the latest version.

@ufrisk Would it be possible to keep all the releases assets (by creating more releases and not changing the assests instead of overwriting the existent assets)? This would ensure that the URL always exists and our package does not break.

If you could go one step further and do not include the version in the asset (only in the release name), our bot could update to the latest version automatically:

• Script that updates GitHub releases: https://github.com/mandiant/VM-Packages/blob/main/scripts/utils/update_package.py#L37
• Example of automatic update the tools cutter and upx that use GH releases: 🤖 Package update mandiant/VM-Packages#1402

[ufrisk]

I added MemProcFS_files_and_binaries-win_x64-latest.zip in the latest release. This download would be the same as the latest download within the release. I may remove this file from non-latest releases.

The reason that MemProcFS updates mid-release on the latest release is cached symbol offsets. I decided against releasing a new MemProcFS version every time Microsoft happens to update some cached symbol offset, but some people would like to use MemProcFS offline so I'd still have to update these offsets.

Anyway, I hope the issue should now be resolved, if you pull MemProcFS_files_and_binaries-win_x64-latest.zip from the latest MemProcFS release.

Please let me know if this fix will do.

Also, Thank You for reporting this issue and for including MemProcFS in CommandoVM and FLARE-VM. It makes MemProcFS more available to people :)

[socketz]

I think with this change it could enough to solve the issue. Thanks for your help!

[ufrisk]

Awesome! And Thank You for letting me know. I'm closing the issue since it's now been resolved.