From owner-freebsd-security Fri Jan 5 12:12: 0 2001 From owner-freebsd-security@FreeBSD.ORG Fri Jan 5 12:11:57 2001 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 1C6D437B404; Fri, 5 Jan 2001 12:11:52 -0800 (PST) Received: from wp2 (wp2.office.ipform.ru [192.168.0.12] (may be forged)) by osiris.ipform.ru (8.11.1/8.11.1) with SMTP id f05KBR834307; Fri, 5 Jan 2001 23:11:27 +0300 (MSK) (envelope-from matrix@ipform.ru) Message-ID: <002f01c07753$af808400$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: "David G. Andersen" Cc: , References: <200101052002.NAA29203@faith.cs.utah.edu> Subject: Re: Antisniffer measures (digest of posts) Date: Fri, 5 Jan 2001 23:11:25 +0300 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > PROBABLE: > > Some kind of tranparent IP encryprtion. > > > > QUESTIONS: > > What kind of IP encryption? > > Is it availbale for FBSD, Linux, WINxxxxx? > > IPsec. IPsec. IPsec. FreeBSD, Linux, Win2k support it. Don't know > about MacOS. Doubt it until OSX, but I could be wrong. This is the > better solution. Well, then i need IPSec for WIn9x, NT 4.x and ME too. Is there? > A final solution is simply to encrypt all sensitive traffic at the > application layer. Use SSL for http/pop3/etc. Use SSH for remote > access. Etc. Not perfect, but works. Nope, dsniff breaks SSL and SSH1. Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message