Hello,
The scientific community makes extensive use of the Icy software.
https://icy.bioimageanalysis.org/
It would be beneficial to package this software for Windows, Linux, and Mac.
Sincerely,
Package request for Icy software
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello again,
This software has the same operational problem, failing to adhere to best security practices in a professional environment. We sent this message to the software publisher on their forum:
We'll see if we can still get it working in program files.
Best regards,
Bertrand
This software has the same operational problem, failing to adhere to best security practices in a professional environment. We sent this message to the software publisher on their forum:
Code: Select all
Subject: Installation path recommendation – conflict with security best practices
Dear Support Team,
I hope this message finds you well.
While reviewing your installation documentation, I noticed that you recommend not installing your software in the “Program Files” directory due to potential permission issues.
However, according to security best practices and government cybersecurity agencies — such as ANSSI (the French National Cybersecurity Agency) and similar organizations like NIST (U.S. National Institute of Standards and Technology) and ENISA (European Union Agency for Cybersecurity) — it is strongly recommended that applications be installed in system-protected directories such as Program Files.
In professional environments, execution of binaries is restricted to trusted paths (e.g. C:\Program Files and C:\Program Files (x86)) to prevent the execution of untrusted or potentially malicious code.
This policy is commonly enforced through application whitelisting and endpoint security controls, which are standard practice in enterprise and government environments.
Would it be possible for you to review your installation process or adjust your software so that it can safely run from within Program Files while maintaining proper permission handling ?
This change would greatly facilitate deployment in secured and compliant environments.
Thank you for your attention, and please let me know if you would like more details about these compliance requirements.
Kind regards,Best regards,
Bertrand
Hi Julien,
when you say "this community," do you mean the scientific software publishers' community?
If so, are you familiar with https://www.eprist.fr/qui-sommes-nous/ ? Could you put us in touch with someone from this association so we can explain this situation, which seems to be becoming widespread?
when you say "this community," do you mean the scientific software publishers' community?
If so, are you familiar with https://www.eprist.fr/qui-sommes-nous/ ? Could you put us in touch with someone from this association so we can explain this situation, which seems to be becoming widespread?
Vincent CARDON
Tranquil IT
Tranquil IT
Good morning,vcardon wrote: ↑Oct 21, 2025 - 7:17 PM Hello Julien,
When you say "this community," do you mean the scientific software publishers' community?
If so, are you familiar with https://www.eprist.fr/qui-sommes-nous/ ? Could you put us in touch with someone from this association so we can explain this situation, which does indeed seem to be becoming widespread?
Yes, I'm thinking of the scientific software publisher community. Packaging this type of software is always a laborious process.
Unfortunately, I have no contact with this association, which I was not familiar with otherwise.
Sincerely,
