The release is now out. This is a critical update! Please update as soon as possible.
If you use Eloquence64 on secure screens, after the update, you must IMMEDIATELY! go to NVDA's settings dialogue, select eloquence from the list box, and press the "copy helper to system config" button again.
It fixes the following issues:
* fix: eloquence64 now clears its log file on start
* Fix: in some cases, eloquence64 could write to its log file at 30 megs per second
* fix: in some cases, eloquence64 created multiple temp files and directories that could not be removed
* fix: in some cases, eloquence64 could unexpectedly leave a port open on the computer
* fix: the port and key to communicate with eloquence could be intercepted by other processes running on the machine
* fix: in rare cases, it could have been possible for other processes on the user's machine to cause the addon to load and run arbitrary Python code by causing it to deserialize an attacker supplied pickle. If the addon was running on a secure screen, this would mean instant privilege escalation.
* fixed: crashing or frozen NVDA will no longer leave orphaned eloquence processes behind
* fix: more reliable pause and break lengths
* security hardening: switch to named pipes with DACL for IPC, ensuring no other process can use the 32-bit host
Release page: github.com/fastfinge/eloquence_64/releases/tag/v21
Direct download: github.com/fastfinge/eloquence_64/releases/download/v21/Eloquence-v21.nvda-addon
@nick Unfortunately, the issue for users of eloquence64 is much more critical than for those of you using eloquence64rs. I am working as quickly as possible to get a fixed release out in the coming hours. However, until that happens, I recommend either not using Eloquence, or switching to Eloquence64rs. Symptoms you may experience: in some cases, eloquence64 may write to its log as fast as 30 megs per second. Eloquence64 does not clear this log file. In some cases, Eloquence64 may create dozens of temperary files and directories, and they may never be deleted. In some cases, Eloquence64 may unexpectedly leave a port open on your computer.Once again, eloquence64rs has fixed all of these issues, or did not experience them in the first place. The code to fix all of the issues in Eloquence64, and clean up the files, has been pushed to my GitHub, but it has not yet been fully tested for functionality. If you build it yourself and it works fine, please do report back so I can get the issues fixed in a public release asap.