|
From: Kevin W. <kw...@co...> - 2025-12-05 11:49:02
|
Question: what problem does this TIP solve, besides messiness? Tempdir litter is not pleasing, but doesn’t the occasional reboot fix that? > On Dec 5, 2025, at 5:23 AM, Donal Fellows <don...@ma...> wrote: > > > A significant part of the problem is that exactly what is allowed and prohibited varies from deployment to deployment, according to the whims of the administrators of the domain, and Windows Defender (the usual tool for enforcing these things) tends to set great store by file names and paths (as well as increasingly by signatures). This situation is "not great" to say the least, especially on development machines. (It usually manifested for me as a persistent failure to be able to run tcltest because "Computer Says No...") > > A mechanism that doesn't require writing out to disk at all is definitely valuable. > > Donal. > > From: Harald Oehlmann <har...@el...> > Sent: Friday, December 05, 2025 09:55 > To: tcl...@li... <tcl...@li...> > Subject: Re: [TCLCORE] CFV: TIP 709: MPL Licence for MemoryModule > > The dll load mechanism was often hit by security issues and is > constantly changing. Perhaps, the "copy to temp and execute" will not be > possible any more in future. It might be prohibitted to store dlls in > the temp folder. Or only "installed" DLLs may be executed. > It might happen, that DLLs have to reside outside of the executable and > be correctly installed in future. I can understand that. Due to that, > the "memory execution" was neat avoiding this issue. > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core |