Re: [Snort-sigs] rsync problem

--On Tuesday, July 31, 2007 10:45:51 -0400 Matthew Watchinski 
<mwatchinski@sourcefire.com> wrote:

> This sounds like its a good candidate for moving to deleted.  The rsync
> protocol is pretty unstructured in places and essentially requires a
> preprocessor to parse and deal with effectively.  We'll give rsync 2.5.6
> and 2.5.7 a diff check out the heap overflow and see if it's fixable, if
> not we'll move it to deleted.  In the mean time I'd suggest disabling it
> in your environment.
What do you suggest using to replace rsync?  It's used quite extensively in 
some places.

--
Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

p7sUaejeAMHyJ.p7s
Description: S/MIME cryptographic signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Snort-sigs mailing list
Snort-sigs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-sigs