Yes, I know: it is not in direct relationship with our project. -------- Original Message -------- Return-Path: <firstname.lastname@example.org> Delivered-To: email@example.com Received: (qmail 27043 invoked by alias); 1 Oct 2006 21:30:39 -0700 Delivered-To: firstname.lastname@example.org Received: (qmail 27040 invoked from network); 1 Oct 2006 21:30:39 -0700Received: from adsl-63-193-97-10.dsl.snfc21.pacbell.net (HELO zaphod.philzimmermann.com) (126.96.36.199) by alpha.total-knowledge.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Oct 2006 21:30:39 -0700 Received: from [10.0.1.201] (adsl-63-193-97-10.dsl.snfc21.pacbell.net [188.8.131.52]) (authenticated bits=0) by zaphod.philzimmermann.com (8.13.3/8.13.3) with ESMTP id k924ReW5031406 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 1 Oct 2006 21:27:40 -0700 (PDT) (envelope-from email@example.com)
In-Reply-To: <45206029.D7EDAF04@RealMeasures.dyndns.org> References: <45206029.D7EDAF04@RealMeasures.dyndns.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <EFE55F1B-0E3F-468E-AB7B-C7FBFDC934CB@mit.edu>Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, rmfxixB1@bobf.frankston.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, mnemonic@WELL.COM, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, Thor@bchands.org, firstname.lastname@example.org, email@example.com
Content-Transfer-Encoding: 7bit From: Philip Zimmermann <firstname.lastname@example.org>Subject: Re: GNU Telephony Releases VoIP Encryption per Zimmermann's ZRTP and RFC 3711
Date: Sun, 1 Oct 2006 21:27:34 -0700 To: Seth Johnson <email@example.com> X-Mailer: Apple Mail (2.752.2)X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on zaphod.philzimmermann.com
I'm sending this out as a group reply to Seth's note. This is just a note to let folks know that today I published a new web site (http:// zfoneproject.com) which announces that my own libZRTP SDK that implements the ZRTP protocol will be available under the GPL. This SDK can be used in many open source projects. I also include a FLOSS exception in the GPL licensing, to allow it to be used in a variety of other non-GPL open source projects.
We're still changing the protocol, to implement video conferencing correctly (we had some protocol bugs in that scenario), but should have that working this week sometime. This will require a change in the ZRTP protocol spec that will cause interoperability problems. You see the perils of premature standardization. I waited 5 years for PGP to mature before introducing the OpenPGP RFC.
I am talking to Werner Dittmann about the changes to the spec for video, so the interoperability issues should be resolved soon enough for his ZRTP implementation.
Phil Zimmermann http://philzimmermann.com (spelled with 2 N's) On Oct 1, 2006, at 5:41 PM, Seth Johnson wrote:
-------- Original Message -------- Subject: Re: Secure Call announcement, for immediate review and comment Date: Sun, 1 Oct 2006 18:04:00 -0400 From: David Sugar <firstname.lastname@example.org> To: Seth Johnson <seth.johnson@RealMeasures.dyndns.org> CC: David Sugar <email@example.com>, firstname.lastname@example.org < SNIP > --- October 1, 2006; Bayonne NJ --- GNU Telephony is happy to announce that with the latest release of the GNU RTP Stack, GNU ccrtp 1.5, we are introducing a free software framework for developing both the secure RTP profile for VOIP (as defined by RFC 3711), and also a GNU GPL licensed implementation of Phil Zimmermann's ZRTP protocol for voice encryption as used in "Zfone". By offering a native secure RTP framework that can be directly embedded in newly developed VOIP applications, GNU Telephony intends to promote the development and widespread use of secure and intercept free voice and video communication services worldwide. The Twinkle softphone package, immediately available with SRTP/ZRTP support, is the first complete free software package to make use of Secure call features offered in the GNU RTP Stack. The GNU RTP stack can be used to develop secure communications for GNU/Linux hosted applications. The stack may also be used to develop application on various BSD systems including Mac OS/X, on Microsoft Windows, and even for embedded systems. We have tested and built the GNU RTP Stack with Handhelds Open Embedded build environment, and we look forward to implementing a Twinkle based secure calling solutions on Linux kernel powered cell phones in the future. Securing RTP sessions is part of our vision in GNU Telephony to help make passive voice communication intercept a thing of the past. By making "secure by design" encryption capabilities simple to embed, and by enabling the largest possible participation in developing such solutions through free software, we hope to break down those remaining barriers that prevent secure telephony from being widely deployed over next generation telephone networks. Part of this vision includes offering TLS encapsulated SIP over TCP, and deployment of anonymous calling proxies, to further deny passive data mining of call session and connection associative information in the future. Downloads: http://ftp.gnu.org/pub/gnu/commoncpp/commoncpp2-1.5.0.tar.gz http://ftp.gnu.org/pub/gnu/ccrtp/ccrtp-1.5.0.tar.gz http://ftp.gnu.org/pub/gnu/ccrtp/libzrtpcpp-0.9.0.tar.gz http://www.xs4all.nl/~mfnboer/twinkle/download/twinkle-0.9.tar.gz Additional Resources: Phil Zimmermann's zrtp specification; http://www.infosecwriters.com/text_resources/pdf/Zfone_SSotillo.pdf. Zfone project; http://www.philzimmermann.com/zfoneproject/index.html. GNU Telephony Secure Calling; http://wiki.gnutelephony.org/index.php/Secure_Call. Twinkle Softphone; http://www.twinklephone.com/. Open Embedded; http://www.handhelds.org/geeklog/index.php. About GNU Telephony: GNU Telephony is a meta project dedicated to the development and promotion of the use of free software for telephony. GNU Telephony is used to directly support the GNU Common C++ family of libraries and telephony application servers such as GNU Bayonne, which are part of the GNU Project, as well as other packages that we regularly use. We will also support several special projects from this site, including CAPE runtime libraries, Secure Calling, and GNU Telephony Open Embedded.
---------------------------------------------- Philip R Zimmermann email@example.com http://philzimmermann.com tel +1 650 322-7223 (spelled with 2 n's) fax +1 650 322-7877 -- Anatoly Volynets, Co-Founder total-knowledge.com culturedialogue.org
Authoright © Total Knowledge: 2001-2008