From owner-freebsd-security Sat Feb 28 10:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00861 for freebsd-security-outgoing; Sat, 28 Feb 1998 10:07:26 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00846 for ; Sat, 28 Feb 1998 10:07:19 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id KAA13619; Sat, 28 Feb 1998 10:06:58 -0800 (PST) To: Atipa cc: Andrew McNaughton , freebsd-security@FreeBSD.ORG Subject: Re: crypto tunnel - international In-reply-to: Your message of "Sat, 28 Feb 1998 10:39:55 MST." Date: Sat, 28 Feb 1998 10:06:58 -0800 Message-ID: <13614.888689218@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk > Some of our customers faced this problem as well, and the simplest thing > to use was OpenBSD. Since OpenBSD has cryptography built in to the OS, it > is very easy to set up secure tunneling. Can you explain *precisely* what you mean by "cryptography built in to the OS?" > OpenBSD is a product of Canada, so they can use full-strength > cryptography. Once it is installed in the US, it is non-exportable, but > the international sites can download directly from Canada :) And we've been exporting said crypto from ftp.freebsd.org as well, which is in a region of the U.S. which falls under Judge Patel's decision. I really don't see what OpenBSD can export which we cannot and it would be really nifty if you could give us details on what is missing from FreeBSD. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message