openssh unix dev - Jun 2007 - patch for triggering SFTP process_write

Hi Damien!

    I produced a little patch to the package ver. 4.6p1 for linux.
My company, for many bureaucratic reasons, was  interested in triggering 
each uploaded file to the server using sftp subsystem.
In Internet and in ML, all folks solve the problem using a script 
joining sftp command section to ssh command section, but unfortunately 
isn't my case.

The patch consist in a modification of sshd_config file. In this file I 
add two new directive for each user who want to trigger the write mechanism.
The new items in configuration file are essentially skipped by 
serverconf.c module: I'll try to be the less invasive I can...
In the other hand, SFTP-server re-read configuration file to catch the 
new items only if the config line contains pw->pw_name, i.e. the 
authenticated user of this sftp session.  Only in this case a new 
struct, called Trigger, is  filled with path and filename of the script 
to be triggered after the OKwrite event.
When calling the triggered script I check the F_OK and the X_OK status 
and, eventually, exit with error: so the client can notice the error too.
If all OK, I perform a fork+execv calling what indicated by struct Trigger.
With many user, I can perform different personalized procedures. 
(thinking at my case this is cool!)

Many stylistic enhancements can take place... but I'm a sysadm :P
I think this patch should be a usefull feature, in this case: nice to 
support the community!

Valerio Balbi     (aka pvb265)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openssh-4.6p1-pvb265p1.patch.bz2
Type: application/x-bzip
Size: 3245 bytes
Desc: not available
Url :
http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20070618/efcc7943/attachment-0001.bin

On Mon, Jun 18, 2007 at 03:48:06AM +0200, valerio balbi
wrote:
> My company, for many bureaucratic reasons, was  interested in
> triggering each uploaded file to the server using sftp subsystem.
I would suggest using a more general approach, such as inotify in
Linux or the equivalent in your system.


//Peter

>Peter wrote:
>I would suggest using a more general approach, such as inotify in
>Linux or the equivalent in your system.
Thank's for the suggestion! I don't know inotify before...
After a first overview to the documentation I confirm my opinion.

It seems easier indicate the script to trigger on write directly into
sftp-server.
It seems strategic to notifiy the error to the sender directly into
the sftp session.

NOK if put or trigger fails
OK only if put and trigger ok

Valerio