-
Notifications
You must be signed in to change notification settings - Fork 4
What does this patch do? #5
Comments
....and this is how HyperDock would equally benefit;
|
You are right, and your approach is faster and safer. You can initiate a pull request, and I will merge it. |
I tried to do this instead of using the .dmg in this repo, and after following tillt's first comment, when closing and re-opening the HyperSwitch application, it prompts me to enable it in accessibility settings despite already being enabled, and then doesn't actually open the application. Turning it off and on in accessibility settings also didn't work. Trying to do @tillt 's instructions in their second comment, I get a "no directory found" for the first line. There's no entry in For context, app worked fine before trying first comment instructions. |
Deleting the app and reinstalling with the original unpatched seems to have resolved the issue? Time will tell. |
You did not read carefully :)
For HyperSwitch, use |
Silly me. Thanks :) |
It appears rather dangerous for anyone to download this patched binary and run it locally. What is extra worrying is that you are not describing what you did to get rid of that popup.
The executable shared here is the original one minus signature and one byte patched;
... patching in a
RETN
and by that shortcutting the function that would check for expiration and nag us.So from my assessment, the results are not dangerous. However, why should anyone trust or believe me? :D
I would suggest instead of distributing a patched binary, go for a live patch of the original on the users' machine. Much cleaner and more transparent - and legally most definitely a better choice.
This should do the same;
The text was updated successfully, but these errors were encountered: