Search Results for: event

Syncplify.me Server! v4.0.32 released

We have just released version 4.0.32 of our Syncplify.me Server! software. This version features the following improvements:

  • Improved: directory list format is now compatible with Maverick’s SFTPv4 behavior
  • Fixed: bug that prevented changing the Software-ID for SSH/SFTP connections
  • Fixed: installer now ensures that all prerequisites are correctly installed before allowing software setup

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Hiding certain files from a directory listing

Syncplify.me Server! version: 4.0.24+

As of version 4.0.24, Syncplify.me Server! has introduced two new features:

  • the BeforeSendDirListToClient event handler
  • the RemoveFromDirList method in the scripting framework

These features can be used together to hide certain files from a directory listing. This is useful, for example, when you don’t want certain users to see certain file types when they connect to your SFTP server, but you still want to show such files to other users.

The first thing to do is creating a script. Let’s assume, for the sake of this example, that you want to hide some AutoCAD® files, and specifically all DWG and DXF files. Then you will need a script like this:

Once the script is ready, you will have to open the user profile you want to apply the rule to, and add an event handler to it, like this: Continue reading

Syncplify.me Server! v4.0.24 released

We have just released version 4.0.24 of our Syncplify.me Server! software. This version features the following improvements:

  • New event-handler: BeforeSendDirListToClient
  • New scripting framework function: RemoveFromDirList(AMask: string)
  • Fixed connection bug in the Command-Line Interface (CLI)

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Making Syncplify.me Server! work with SSHFS/WebEx

Syncplify.me Server! version: 4.0.19+

SSHFS is a FUSE-based filesystem client for the SSH File Transfer Protocol (SFTP); it’s very common among Linux users to mount SFTP targets as local directories. WebEx is a well-known teamwork collaboration tool by Cisco that uses SSHFS to back-up its data to a remote SFTP server.

Unfortunately, the coupling of SSHFS/WebEx – at the time this article is being written – has at least two problems that can cause serious issues to servers that implement the SFTP protocol and its extensions correctly. Continue reading

Syncplify.me Server! v4.0.17 released

We have just released version 4.0.17 of our Syncplify.me Server! software. This version features the following improvements:

  • Added: new bearer-token authorization mode for the REST API (and updated the help/documentation accordingly)
  • Added: [%USER_DESC%], [%TODAY%] and [%SESS_CUSTDATA%] in VFS base path definition
  • Fixed: bug that prevented JSCH-based clients from downloading files correctly

As usual you can download this new release from our website.

The Journey from FTP to SFTP

You can also download this white-paper for offline use by scrolling to the bottom of this article.

File transfer is an important aspect in computing. There is always a need for us to transfer files between a source and a destination. While in the earlier days, certain protocols were used to manage file transfers between the client and server, security was not much of a concern then. But, with the advancements in computing and rise of different kind of intrusions, security gradually became a pressing need. Yes, you guessed right. I am talking about FTP and SFTP. Let’s take a look at the journey from FTP to SFTP.

The standard network protocol File Transfer Protocol (FTP) is used to transfer files between a client system and a server. According to Wikipedia, the FTP ran on NCP specification until 1980. After that the protocol was replaced by a TCP/IP version named RFC 765 and consequently by RFC 959 in October 1985. RFC 959 is the current specification which FTP follows.

According to the latest specification, FTP should fulfill 4 major objectives namely: Continue reading

Syncplify.me Server! v4.0.16 released

We have just released version 4.0.16 of our Syncplify.me Server! software. This version features the following improvements:

  • Added: compound percentage index to improve Protector™
  • Improved: directory listings now feature attribute-placeholders for virtual directories
  • Improved: better checking of target syntax for all VFS types
  • Fixed: bug in the scripting framework that prevented scripted wildcard (catch-all) user authentication
  • Fixed: DiskAES256 VFS encryption-key change is now (correctly) disabled
  • Fixed: various glitches in the web interface

Note: we skipped version 4.0.15 as we used such build number internally for some laboratory tests.

As usual you can download this new release from our website.

Authenticating users against your own DataBase

Syncplify.me Server! version: 4.0.16+

Note: in order to use the code posted in this article you need to be running at least version 4.0.16 or greater of Syncplify.me Server!

As you all know, Syncplify.me Server! already supports its own internal users, as well as Windows and Active Directory users (and groups, depending on the license type). Yet, some of our customers need to implement totally custom authentication methods, often based on their own user databases.

In this article we will show one way to do so. This is clearly just meant to serve as an example, and real-life scenarios require some further customization to the DB and the script posted here. But it’s a fairly decent starting point.

So, the background scenario for this example is:

  • our users’ authentication data are stored in a Microsoft(R) Access database
  • in our DB, each user is associated to a “category” (in this case his/her department: sales, marketing, …)
  • for the sake of this example, all users’ passwords are set to “password” (without quotes)
  • the script is pretty sophisticated, because besides authenticating the user, it will load a user profile that belongs to the “category” of the user from the main Syncplify.me Server! user-base

So let’s start taking a look at our user database: Continue reading

Scripting lesson: using scripting and session info

Syncplify.me Server! version: 4.0.13+

This articles shows how to use scripting, event-handling and session information from within Syncplify.me Server! For the sake of this example we will only log such information in the log file, but in real-life production scenarios you can use these info as you wish (for example you may want to send them via email to someone, or even make decisions based upon them).

Let’s start by preparing the script that – as we said – will log some info in your Syncplify.me Server!’s log file:

We save the above script with the following name/description: “Log several client and connection info”.

Then we add an event-handler to trigger the execution of the script. Since the script contain references to file-transfer-related variables (VirtualObjectName and ObjectName) it seems obvious to trigger its execution upon occurrence of a file-transfer-related event. For the sake of this example we have chosen the AfterFileUpload event, which occurs every time a file is successfully uploaded by a client onto the server. Continue reading

Syncplify.me Server! v4.0.13 released

We have just released version 4.0.13 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed a bug in the DiskAES256 encrypted Virtual File System (VFS) – this bug prevented files from being correctly downloaded if the client requested odd-sized or unaligned buffers

Very important: to fix this bug we had to change the way we encrypt files at-rest via DiskAES256 VFS; so if you use this particular type of VFS, please, make sure you download all your files to a non-encrypted location before you update to 4.0.13, after the update please delete all files from the location that was protected by the DiskAES256 VFS and re-upload them all. We sincerely apologize for the hassle.

As usual you can download this new release from our website.