Releases: RobotsOnDrugs/Moo.NoBlockInput
Releases · RobotsOnDrugs/Moo.NoBlockInput
v0.8.1
- Added a log level configuration option. See the configuration page for details. The default level is debug for debug builds and info for release builds.
- Fixed a hook bug that could cause issues with UltraViewer and Remote Utilities.
- Added the ability to build only debug binaries, only release binaries, or both at the same time in the build script. The switch has changed from
-BuildDebugto-Build ['DebugOnly' | 'ReleaseOnly' | 'All'] - Added
-AdditionalOutputDirsto the build script to specify any additional directories to copy the binaries to. - Fixed a few minor issues with the build script and added a PowerShell version check.
- Made some minor bugfixes.
v0.8.0
- Breaking change: nuked support for the TOML configuration file. All configuration must be made in the registry.
- Added a condensed configuration readme.
- Several bug fixes related to configuration, particularly with handling missing registry entries.
- Fixed a bug in the build script where manifest versions of each project would not be compared properly.
- Made some other minor fixes.
v0.7.2
- Fixed issues with module ejection, preventing crashes.
- Fixed default registry files.
- Logging is filtered to prevent messages from dependencies.
- Tested and fixed issues with Iperius Remote, and added it to the default configuration.
- Consolidated binary release archive to include both debug and release versions.
v0.7.1
- Fixed compatibility issues with UltraViewer and Supremo.
- Added more error handling for DLL injection and ejection.
- Added more remote desktop software process names to the default configuration.
v0.7.0
- Added logging for both the terminal and log files.
- Updated the registry entry files to add LogDirectory.
- Improved validation of configuration for both registry and the TOML file.
- Improved output (now logging) messages from the injector.
- Removed allocation of a console for hooked processes in the debug version since there is now logging to file.
- Binary releases have updated dependencies.
v0.6.0
- Bumped version to 0.6.0.
- Added the ability to configure the state of hooks.
- Configuration can now be done via the registry, and BlockInput/SendInput hooks can be enabled/disabled via the registry.
- If there is no configuration in the registry, injector.toml will be used.
- Added .reg files with the defaults (matching injector.toml).
- Moved injector configuration code into its own file.
v0.5.0
- Remote input is now blocked as well while the module is injected.
- Sending Ctrl-C to the injector cleanly ejects the module from all target processes.
- The build scripts support setting manifest properties of the binaries.
- The README has been updated to reflect the fact that support for injection is nearly universal and there is no need to track individual remote desktop applications.
- The debug build creates a console for target processes. It does nothing useful in this release, but sets up for further work. Release builds do not do this.
v0.4.0
- Changed from hardcoded values to configurable ones. Processes to hook, the process trace name, and the name of the DLL to inject are now configurable.
- Ctrl-C now stops the trace.
- Fixed version information in build.rs.
v0.3.1
Add support for SupRemo.
v0.3.0
- Added support for injection of 32-processes, specifically Remote Utilities client (aka the "Agent" or "Host"). The 32-bit injector will not attempt to inject into 64-bit SC client and the 64-bit injector will not attempt to inject into 32-bit RU client. Note that this tool does not unhide the Remote Utilities black screen.
- Added a build script to make it easier to build and collect the binaries for both x86 and x64.
- Added a
build.rsfor embedding a manifest to the injector to automatically request elevation. Removed a couple minor testing artifacts and reorganizedusestatements a bit. - Added a debug build which prints a little information to the console. Release builds will never spawn a console, but debug builds will, so it is not recommended to use debug builds during real scambaits. Proper logging coming soon™.