maumsti

Hello, a new version (3.0.0) of my component is now available. It introduces the use of Named Pipes for communication between the Agent and clients.

Hello aehimself, Yes it's for this reason that I wrote this application. I place my executables on a network drive and I cannot afford to have one or the other on a different version. I also have the problem that a certain number forget to exit the application and you cannot replace the executable as long as it isn't released by everyone. My application allows this under better conditions because it tries to close applications in a clean and secure way. Since my first publication I have completed my application (version 2.0.1) with a module that allows automatically copying executable files from a source directory to the shared directory. You just need to maintain an updated list of programs that you want to manage in this way.

Yes, we need to do what is necessary for security. I am thinking of first modifying the communications between the agent and the applications by using Named pipes. In a second step, I will work on using TLS between the master and the agents.

Thank you for your feedback! Security is a key concern, and I have planned to secure all communications using TLS encryption. This is precisely why I chose TCP instead of UDP—to leverage TLS easily and ensure message integrity and authentication. With TLS, only authorized clients will be able to send and receive commands securely, preventing unauthorized shutdowns or deployments. UDP could be useful for discovery, but for executing critical commands, TCP with TLS provides much stronger protection. That being said, if a malicious actor has already gained access to the network, their primary goal would likely not be just shutting down applications but rather compromising systems, exfiltrating data, or escalating privileges...

Hello Delphi Praxis community, I'm excited to share my new open-source project, AppWatcher: https://github.com/mbaumsti/Delphi-App-Watcher Have you ever faced the challenge of managing dozens of Delphi applications running on multiple network machines? Finding a convenient time window to replace executables can be a real headache. That's why I developed AppWatcher. AppWatcher is a Delphi component and applications that allows you to remotely control the stopping and restarting of your Delphi applications across your network. Here's how it works: Integrate the TAppWatcherClient component into your Delphi applications. Deploy the AppWatcher Agent on your client machines. Use the AppWatcher Master application to remotely control all your applications. Key features: Remotely stop applications with user notifications. Automatically restart applications after updates. Avoid using RDP or physically accessing each machine. Minimize downtime and streamline deployment. If you're looking for a solution to simplify remote application management in your Delphi environment, I encourage you to check out AppWatcher. Contributions and feedback are welcome! Thank you,