Dear list members, developers,

in our heterogenous network (Linux, Windows, Mac) we have the requirement to
check incoming data streams for viruses and other malware.

Scanning email seems the easiest part here, also scanning directories
regularly. These are all server bound.

You can set up Windows machines to scan hotplugged devices (USB-Sticks, HDs,
etc) with the installed virus checker.

A current problem is the handling on the ltsp thinclients. Although Linux on
the clients and on the ltsp-servers minimizes the problem with malware
enormously, the data is stored in public directories, where also Windows
machines have access to.

I found hints for binding clamfs (http://clamfs.sourceforge.net/) into the
fuse mount process (see
http://muzso.hu/2010/07/08/how-to-make-truecrypt-work-for-normal-users-and-with-ltspfs-mounted-local-devices-eg.-usb).
But this needs source code changes in the ltspfsmounter script which have to
be redone after each update.

As this is a common problem for lots of network administrators, I wonder if a
generic solution would be available/desirable.

Has anybody implemented this or other useful hints?

Thanks in advance.
Helmut

-- 
-------------------------------------------------------------------------
Helmut Lichtenberg  <helmut.lichtenb...@fli.bund.de>  Tel.: 05034/871-128
Institut für Nutztiergenetik (FLI)         31535 Neustadt         Germany
-------------------------------------------------------------------------

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to