Parametric home directories

Syncplify.me Server! version: 4.0.26+

Another highly requested feature that we introduced in Syncplify.me Server! v4 is parametric home directories.

Some of our customers, in fact, need to isolate every user in their own directory under a general “container”, the directory name being the same as the user’s username. They also requested that if a particular user’s home dir does not exist, it is automatically created when the user logs in.

A structure like this:
C:\SFTPData
+----------\user_one
+----------\user_two

This is how you do it in Syncplify.me Server! v4. Continue reading

Syncplify.me Server! v4: the Virtual File System (VFS)

Syncplify.me Server! version: 4.0.0+

One of the biggest additions to the upcoming version 4.0 of Syncplify.me Server! is the VFS (Virtual File System) support. But what is it exactly? And what advantages does it bring to our users?

Let’s start by setting the bar with v3. Our version 3.x, in fact – as nearly every competitor – allows you to place users’ “homes” (root directories) on a disk. It can be a local or a network disk, but it’s basically disk-based. The following picture explains the concept in a visual way: Continue reading

Maintenance release: Syncplify.me Server! v3.1.24.64

We have just released version 3.1.24.64 of our Syncplify.me Server!

This new maintenance release introduces a measure to deal with non-standard client softwares that send paths with multiple slashes (ex: ////documents//mydoc.xls). Even though this is a client-originated protocol violation, we needed to make sure to manage it correctly on the server-side in order for the client to be able to reach the intended file. Now all paths are correctly normalized.

As usual you can download the latest version from our web site. Thank you!

Syncplify.me Server! v4 Test: 200,000 files in 1 folder

Syncplify.me Server! version: 4.0.0+

We had customers reporting that Syncplify.me Server! v3 session threads may stall (and use up an entire CPU core) during directory listing if a single folder to be listed contains a large number of files, say north of 20,000.

First we tested our v3 to confirm the issue, then we tested many other FTP/SFTP servers, and found out that none of the tested competitors passed the test either. Some of them crashed around 10,000 files, the best ones crashed around 65,000.

Then we tested our own new Virtual File System that comes with Syncplify.me Server! v4… and, well, we think that a picture is worth a thousand words: Continue reading

Syncplify.me Server! v4: Encrypted File System

Syncplify.me Server! version: 4.0.0+

One of the most anticipated features that Syncplify.me Server! v4 will deliver is the ability to mount virtual directories – even nested ones – as encrypted virtual file systems.

fzfolders

The Encrypted VFS transparently encrypts and decrypts data on-the-fly during uploads and/or downloads, making sure that the files at-rest on the server side are always encrypted. This way you can run your server externally, and still always be sure that who operates the server for you doesn’t have access to your files/backups. This is also a requirement in some cases when your company has to comply to the PCI/DSS or HIPAA regulations. Continue reading

FTP Script! lesson: using the new features in v3.1

Syncplify.me FTP Script! version: 3.1.0+

FTP Script! v3.1.0.50, released earlier today, comes with a bunch of new features and functions to simplify some tasks related to the management of local files. In fact, it’s not just about transferring files to/from FTP servers… what you do with those files after/before you upload/download them to your local disk also matters!

In earlier versions of FTP Script! the FileCopy function, for example, was very limited. It could copy only one file at a time, and it had no support for wildcard file masks. In v3.1 we greatly improved it, and you can now use it this way:

The third parameter (set to true in the example here above) determines whether the function should overwrite the destination file(s) if it/they already exist.

Continue reading

New release: Syncplify.me FTP Script! v3.1.0.50

We have just released version 3.1.0.50 of our Syncplify.me FTP Script!

This new version comes with a series of nice improvements and additions to the local file management functions, such as:

  • The FileCopy function now supports wildcards and an optional Overwrite parameter
  • A brand new FileMove function, with the same parameters and usage criteria as the FileCopy function here above
  • A brand new FileEnum function to search for files in directories that supports wildcards and optional recursive search in subdirectories

As usual you can download the latest version from our web site. Thank you!

Syncplify.me Server! v4: the all-new VFS

Syncplify.me Server! version: 4.0.0+

One of the biggest changes that version 4 will bring to Syncplify.me Server!’s user base is the all-new Virtual File System. This is such an epic change that it’s actually one of the reasons why the release of v4 is taking longer than expected… but it will be worth the wait.

Check out the following comparison table to appreciate the main advantages of the new VFS over the previous approach (that was based on “virtual directories”):

Virtual Directory Approach (v1, v2, v3)Virtual File System (v4)
Virtual directories can only be placed directly under the user's home directoryIn a VFS, virtual folders can be placed anywhere, even nested within each other
All virtual directories are accessed "as" the user who logged in (single impersonation)In a VFS, each virtual folder can accessed "as" a different user profile (multiple impersonation)
Virtual directories mapped to UNC paths could not be accessed by "normal" user profiles, only by Windows or AD user profilesEach virtual folder has its own impersonation criteria, so even "normal" user profiles can access virtual folders mapped to remote UNC paths

Continue reading

Maintenance release: Syncplify.me Server! v3.1.1.41

We have just released a maintenance version of Syncplify.me Server! This new version fixes a tiny glitch that prevented the software from saving the log files in the correct folder under certain operating system locale configurations.

If your log files are saved in the right place, you don’t need this update.

As usual, you can download the latest version from our web site.