From owner-freebsd-security Sun Nov 8 12:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15595 for freebsd-security-outgoing; Sun, 8 Nov 1998 12:11:20 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15589 for ; Sun, 8 Nov 1998 12:11:17 -0800 (PST) (envelope-from security@tasam.com) Received: from localhost (security@localhost) by tasam.com (8.9.1/8.9.1) with SMTP id PAA18898 for ; Sun, 8 Nov 1998 15:10:58 -0500 (EST) Date: Sun, 8 Nov 1998 15:10:58 -0500 (EST) From: Security To: freebsd-security@FreeBSD.ORG Subject: Re: port 1080 scans In-Reply-To: <199811080938.KAA06024@gilberto.physik.RWTH-Aachen.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've noticed our socks5 dumping core quite often. It's stopped now, but about a week ago it was acting up. On Sun, 8 Nov 1998, Christoph Kukulies wrote: > In our campus network we are increasingly observing port > scan attacks from outer sites on port 1080 (socks). > > Does anyone know of any recent security hole related to this service > on any platform (possibly linux - but I want to be prepared wrt FreeBSD). > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message