No Syncplify software uses (nor has ever used) anything written in Java. Furthermore, and more specifically, no Syncplify software uses (nor has ever used) Log4j. Therefore, none of our software is affected by (nor it has ever been) any Log4j bug or vulnerability.
Recently we had the chance to help one of our customer achieve a data synchronization task, which spawned an unusual cooperation that gave birth to a tale worth telling. So, here we go. Our customer was using Syncplify.me AFT!, our scriptable secure file transfer client, to automate some unattended data synchronization tasks. One of these […]
Yes, V6 is the most anticipated Syncplify Server! version since the software was first released back in 2014… but for our company, and for our customers, it means much more than that. In fact: Together with it, we will also release our first Customer Control Center, through which our customers will be able to perform […]
This is a technical blog. And it has two main purposes: 1) To share ideas and insights into the development of the next features in Syncplify’s products with other developers and system administrators who routinely use our software 2) To publish Release Notes every time a new version (whether it is a minor update or […]