PGP Creator's Zfone Encrypts VoIP

Philip Zimmermann, creator of PGP wrote in to tell me about Zfone, his new system for encrypting any SIP VoIP voice stream. His first release is Mac & Linux only. I tested it with him using Gizmo as our client and it was pretty trivial to use. While it should work on most any SIP compatible VoIP client, he hopes that clients like OpenWengo and Gizmo will incorporate Zfone directly into the UI. Zfone has no centralization, and has been submitted to the IETF. He hasn't yet determined a license, but he believes strongly in releasing source code for all encryption products. A windows client is forthcoming.

typo

>His first release is Mac & Linux only.

you misspelled Windows.

oh... that makes a refreshing change.

My only concern

...is that the US (yes, I live there) will use security fears relating to terrorism to ban or severely restrict this technology. Some elements of our government seem almost Luddite (http://en.wikipedia.org/wiki/Luddite [wikipedia.org]) these days.

Sad, because this kind of encryption would permit greater use of this technology in medicine under HIPPA privacy regulations.

Re:My only concern

I'd say it's dissapointing that the post had to link to a definition of Luddite in the first place.

It would also..

It would also almost totally negate any ISP's attempt at shaping VOIP traffic to try and get people to buy their service instead. This has been somewhat of a question in recent months, but if you can encrypt your stream, then there's not much chance they can slow your packets. I'm all for the increased security as well. Now if we can only get them to cut down on the spam....

Re:traffic shaping reality check

The mention of 911 gives me an idea for an interesting angle to ensure ISPs can't neuter VoIP.....claim that by doing so they're endangering lives in the event of a 911 call.

Re:It would also..

Hence we are back to stenography.

Is that shorthand for steganography?

Encryption

Let's be honest -- this guy needs to go to jail NOW. Privacy is almost as treasonous as sharing or questioning your leaders.

Re:Encryption

Privacy is almost as treasonous as sharing or questioning your leaders.

no, sorry, you can keep Bush... do not share him...

My security fears

I don't live in the US but I live very close and almost all of my IP traffic travels through the US at some point and my worry is that any business information collected by the US/CIA/FBI or other US agency would be made available to US companies. There have been court cases in the past of US sponsored spying benefiting US companies. They say they are after terrorist but who knows? With the knowledge of past activities of US spies and the current computing power of the US agencies all foreign businesses would be well advised to encrypt all sensitive information.

http://www.motherjones.com/news/feature/1994/05/dr eyfuss.html [motherjones.com]

http://web.nps.navy.mil/~relooney/4141_Spring2002. pdf [navy.mil]

http://www.commondreams.org/headlines/070200-02.ht m [commondreams.org]

Not using encryption is to believe GWB when he says "Trust me"

Important Stuff

This is important stuff as more and more phone traffic is routing open in the internet. While most people do not believe their emails are totally private, when it comes to talking on the phone I believe there is a perception (and assumption) that no one else is listening. SIP, Asterisk and all the flavors of VOIP is changing telecom and encryption is necessary.

I agree, it is hugely important

Hopefully, this will be the straw that breaks the camel's back.

Ultimately, ALL traffic should be encrypted, whether it is VOIP, email, web browsing, whatever.

The guy is right when on his home page he talks about how it is so difficult to implement this sort of stuff as an add-on for emails, managing keys and the like. It's why no one does it. Of course, there has always been a computing overhead, also, which is why only pages that "need" to be secured currently are. But as horsepower goes up, those limitations should go away.

Ultimately, it should be a matter of course before all traffic that goes in our out of your computer is encrypted by default.

Hopefully this is the start of something huge!

Steve

Re:I agree, it is hugely important

yes, but the nice thing is that for most encryption methods, the work to do the encryption grows linearly (at worst polynomially), whereas the work to break the encryption grows exponentially in key size. the larger the key gets, the bigger the gap between work to encode and work to decode.

Re:I agree, it is hugely important

Almost all commercial multiplayer games use encryption as security-through-obscurity, usually by using custom algorithms. In online games, you're trying to keep cheaters from manipulating packets, not keep eavesdroppers from watching.

For https and such, setting up the connection is the majority of the work. Public-key key exchange (public-key certificates, Diffie-Hellman, etc.) is an expensive operation because it requires a modular exponentiation on the part of the server. However, once the connection is set up, the cost of encrypting each packet is extremely small.

Melissa

Phil and Jon

For some reason I got to thinking about Phill Zimmerman and DVD John [Johansen]. Both seem to pop up now and then and give us all reasons to smile.

Hmm... I wonder if Phil could come up with security that Jon couldn't find a way around?

Ob. Simpsons Ref

Could Phil microwave a burrito so hot even Jon couldn't eat it?

Re:Phil and Jon

I'm sorry, did I miss the story about DVD John breaking the public key encryption model? And blowfish? And the cypher du-jour?

He's released cracks for various pieces of software, but it's not like the guy's actually broken actual strong encryption algos.

http://en.wikipedia.org/wiki/Jon_Johansen#Other_pr ojects [wikipedia.org]

Re:Phil and Jon

He's released cracks for various pieces of software, but it's not like the guy's actually broken actual strong encryption algos.

And such 'cracks' are the best way to attack otherwise strong crypto-systems - don't try to crack an algorithm -- crack the implementation. Look for the vulnerabilities in the systems that use strong cryptography and find the back-doors, or break in a hole in the wall, but trying to go mano-a-mano with the entire crypto community isn't a smart thing and you are exactly right -- that isn't what DVD-Jon has ever done.

Not that I would imply that CSS is a strong algorithm, it ain't. But the new stuff for BLU-HD-RAY uses AES and the stuff that the Zim-man is using to security VOIP also uses tried and true crypto algorithms. That doesn't mean there won't be flaws in the implementations that can be exploited and Jon-Jon He's Our Man, If He Can't Exploit It, No One Can!!! Yeah Jon. Or something like that.

Releasing the source

If he releases the sources won't companies like Vonage that are being subjected to voip packet throttling from copetitive ISPs just take it and use this technology for free?

Re:Releasing the source

Wouldn't that kinda be the point?

What ever happened to PGP Phone?

The MIT Website [mit.edu] has taken it down, but I remember it working somewhat well between two IP address.

Was it just too far ahead of its time?

No PKI?

Would it be useful to have the option, for those of us who have friends' PGP keys, to do the Zfone key handshake via PGP encryption that rather than verifying something by voice? It's fantastic from a "getting people to use it" perspective that it does not rely on PKI, but those who have already taken the plunge shouldn't be punished :)

Why not encrypt by default

This article has me wondering about something. Why aren't we encrypting things by default? Why isn't encryption being built into the protocol when it's designed? It always seems that it gets tacked on afterwards, if at all, and we're worse off in the long run for it. Take VNC for example. If you want that encrypted you're told to send it over SSH. Wouldn't it be great if VNC traffic was encryped by design right from the start? The same applies to any other traffic (VoIP, IM, whatever). What happens is that many people don't encrypt because of the difficultly or they don't know any better. Unencrypted traffic is sent putting them at risk.

We know the network is hostile and retrofitting encryption onto something after the fact doesn't always work either because too many people using the unencrypted protocol, it's too hard to configure (as opposed to being mostly automatic like ssh connections), or just general security ignorance. What's really holding us back?

Encryption is hard

Because encryption is very difficult to do correctly. And we should all know by now that a false sense of security is worse than no security at all.

There's also the not insignificant fact that encryption is complex to use and administer. Adding in robust encryption is not free from a user-friendliness perspective. Much thought has to be put into reducing the user-visible complexity as much as possible so that the user base will actually use the encryption, and use it in such a way that security is preserved. Not trivial.

Re:Why not encrypt by default

This article has me wondering about something. Why aren't we encrypting things by default? Why isn't encryption being built into the protocol when it's designed? It always seems that it gets tacked on afterwards, if at all, and we're worse off in the long run for it. Take VNC for example. If you want that encrypted you're told to send it over SSH. Wouldn't it be great if VNC traffic was encryped by design right from the start? The same applies to any other traffic (VoIP, IM, whatever). What happens is that many people don't encrypt because of the difficultly or they don't know any better. Unencrypted traffic is sent putting them at risk.

There are lots of reasons why encryption isn't being widely used. For one thing there is the normal tinfoil hat reason, ie. that the people in charge don't want it becausy they wouldn't be able to stick their nose where it don't belong so they try to prevent such technology from being widely used. Alot has also to do with cost and computing overhead. Encrypting can be an expensive thing to do in terms of computing power and especially so if everything form all the network communications protocols to storage media content is bening encrypted. Doning encryption with special hardware is one solution but that adds cost and also the problem of the hardware algorithms becoming obsolete like WEP for example. Just try to get ahold of, say a 100mb photoshop file. Now copy it into the user home directory of a regular user on an OS.X machine, then do the same for antoher user using 'File Vault'. You will quickly discover that the latter operation takes alot longer since those 100mb's of Photoshop file are being encrypted. You should notice similar problems when comparing normal unencrypted file transfers over a network with transfers over a high strength encrypted link. VPN for example works noticably slower using port forwarding over an SSH tunnel.

Re:Why not encrypt by default

• Technological
  
  • Encryption implementation isn't free.
    
  • Encryption maintenance isn't free.
    
  • Unencrypted traffic is easier to sniff (which may be legitimately important).
    
  • Encrypyed traffic has a higher CPU overhead (which isn't always made up for).
    
  • Some people prefer to have one really good encryption program (SSH or a VPN) to route all traffic over.
    
  
  
• Legal
  
  • Encryption can't always be exported from every country to every other country.
    
  • Sometimes it may be illegal to encrypt traffic.
    
  
  

Re:Why not encrypt by default

Why isn't encryption being built into the protocol when it's designed?

For any IETF protocol developed in the past 10 years or so, it is. For example, RFC 3261 (which defines SIP) makes TLS encryption *mandatory* to implement. It does allow the users/administrators/whatever to turn it on and off, but you can't say your implementation is RFC 3261 compliant unless it contains TLS encryption.

For most other important protocols defined before the IESG required strong security in all protocols, there have been significant efforts to revise them as necessary to provide encryption. For example, RFC 3711 defines a mechanism for encrypting RTP (the voice packets in a VoIP call).

Anyone who bothers to actually implement to spec already has released products that do encryption, many by default. For example if I use the Snom 360 SIP phone on my desk to call anyone else using a client that has actually implemented all of RFC 3261 (instead of whatever small portion of it amused them) and implemented RFC 3711, both the signaling and the media will be strongly encrypted BY DEFAULT. And that's the way it was configured when I took it out of the box.

The fact that some current implementations don't bother following spec impugns their designers and implementors, not the protocols they're using. Using the standardized VoIP protocols available today, everyone *should* be able to make encrypted calls.

great

great idea, this is very much needed. I don't know how secure this actually is, the writer (phillip zimmermann) said he builds the encryption into tcpstack of whatever operating system the user is running and the key exchange is done automatically between hosts.. he also makes the statement that this technology/standard (zfone) would be integrated into the end-user software, in the near future. I'm not sure why he's so confident, it's nice but who's to guarantee any sip softphone end-points or better yet, hard telephones, will actually have this built in.

hmm.. i wonder if I have linux nat router running this (and it being my default gateway, if it will automatically encrypt any sip sessions if the end system is running the zphone gui. I mean this apparently works at the network layer (like tcpdump, promiscuously), I wonder if it has to be running on the same system the sip session is originating from. oh dear, i really need to replace my dlink router these days.

Checksums, distro needs sigged.

As there is no cryptographic signature on the package, these are my sums
as received. Please compare and post if yours are different.

SHA1 (zfone-linux.tar.gz) = aa9ac66a5dce43cff2639787f30e939078b47ebe
MD5 (zfone-linux.tar.gz) = c6a47feca0fd5cb5bf72a8f6a1e8f207

PRZ, please sign your packages! Thanks, World.

SRTP?

What's the difference between this and SRTP [ietf.org]?

PGPfone, Speak Freely

I can remember Phil's PGPfone [pgpi.org] which was released before VoIP was "the next big thing." It used GSM speech compression and 3-DES/CAST/Blowfish cryptography "to give you the ability to have a 'real-time' secure telephone conversation" (directly over 14.4 Kbps (or faster) modem-to-modem, through the Internet, or through AppleTalk).

That died. It is good to see a new alternative that has adopted newer standards.

Another "oldy but goody" was Speak Freely [speakfreely.org].

Related project

There was a presentation from another group (wasn't Phil, although he was there) at DefCon 13 relating to reverse-engineering the GSM voice compression so that data could be fed through a GSM voice link accoustically with almost no overhead (in other words, at close to the GSM native digital bandwidth). The intent being to provide a means to attach accoustic peripherals (handsfree headset for example) that could perform encryption and send the encrypted, digitized voice over the GSM link accoustically (to be recieved and decoded by a similar device on the other end), thus allowing encrypted voice communication over an untrusted and unmodified cell phone without the need to install any software.

Who needs encryption?

Igpay atinlay isway ethay estbay ayway otay encryptway ouryay onversationcay!

Ekiga?

Any Ekiga [ekiga.org] (formerly GnomeMeeting) devs care to comment on whether they'll support this?

Well...

SIP is just a protocol that sets up connectivity and media control; the stream itself is not covered by the SIP protocol. For that, you need something that supports Secure RTP (SRTP), which encrypts the payloads of all RTP streams. If you've managed to encrypt SIP, all you're doing is encrypting call setup and feature requests. Your conversation is not encrypted.

VoIP and IM

I'm thinking MSN Messenger and Google Talk should add this to their VoIP features. Right now talking with VoIP unencrypted over the 'net makes me a bit uneasy.

However, though encrypting your VoIP communications might make them more secure, they're also much more likely to be flagged by systems like ECHELON, which automatically tag traffic that is encrypted as suspicious.

In other news...

Philip Zimmermann has apparently vanished from the face of the earth. Film at 11.

Why not use OpenSSL?

I know the API isn't the greatest and the documentation completely sucks but someone with OpenSSL knowledge could put together a SIP-friendly API in a couple hours.

At least then you're using a public, well hammered on API and would have a multitude of algorithms to choose from. I mean OpenSSL is used in tons of stuff and gets lots of field testing.

I have never understood the point of PGP with its proprietary crap formats when there are open, standardized formats for the stuff it is typically used for (S/MIME, X509, PKCS#12, etc.) and that are supported in standard applications rather than require some goofy PGP add-on.

Re:Why not use OpenSSL?

VoIP is different from most other traffic types in that it is hard realtime and needs real low latency. This means VoIP uses UDP

OpenSSL builds encrypted sessions over TCP. TCP is not designed to work well for the requirement space needed by VoIP.
If fact, it just would not work well at all.

Re:Why not use OpenSSL?

OpenSSL is not just an SSL API. It's a full cryptographic API. The socket stuff is not even in the core crypto library. There is libssl and then there is libcrypto. Both are part of OpenSSL.

OpenSSL is a misnomer.

I didn't mean "use SSL", I meant use OpenSSL the cryptographic library that supports all that standard stream ciphers. You can use whatever networking stuff you want outside of OpenSSL.

Getting this thing to build under Linux

I've not been able to get this thing to build on FC3, FC4 or Debian-Stable. In zfone-linux/srtp-ctr some of the test utilities won't build... no big deal because make install still works. The makefile for zfone-linux/libzfone/bnlib references /bin/install instead of /usr/bin/install. No biggie. Fixed. Installed. Lastly (I stopped here), make of zfone-linux/libzfone totally blew chunks in what at first glance looks non-trivial.

Methinks Phil needs a Linux box!
hehehe j/k.

Has _anyone_ got this thing to build?

What is the big deal?

Why do some people jump all over protocol-specific encryption as helping terrorists, or other such nonsense?

There is a great deal of concern over Skype being encrypted. People say it can be used by terrorists for encrypted communication. The thing is, throw up a VoIP server of some kind (Even the free ones like Ventrilo or TeamSpeak), and connect to it using something like Hamachi. Bam! All your UDP voice traffic is encrypted.

Heck, you can even do it with TCP. SSH tunnels encrypting two-way Shoutcast streams. Huzzah! Encrypted two-way voice communication! Heck, pump the shoutcast stream over HTTPS and that'd be encrypted too.

So, this is why I don't get it. Why complain about Skype when there will always be ways to encrypt voice traffic over the internet? Programs like Hamachi (Encrypted P2P VPN solution with an IM-like interface) make it insanely easy to set up more secure solutions than Skype, and there is always SSH tunnels as a fallback.

So how does this relate to the current situation? Well, people are sure to complain that this new program somehow helps terrorists. So I'm just saying that that is BS.

QoS

Hmmmmm, could one use this method to get around some of these pesky Quality Of Service restrictions? Because we all know the carriers like to enforce these things to keep you from getting quality from your VoIP service.

Is Phil marrried?

I have a 22 year old sister that I'd like to introduce him to.

I NEED a guy like this in the family.

LK

Is this trialware?

I installed it and rolled the system clock a few years and it still seems to run. Section 2 of the license agreement, however, says:

2. Term. THE SOFTWARE MAY CONTAIN A TIME-OUT FEATURE THAT DISABLES ITS OPERATION AFTER A CERTAIN PERIOD OF TIME OR AFTER A DATE SPECIFIED IN THE SOFTWARE (the "Expiration Date"). The term of this Agreement ("Term") shall begin when you download or install the Software and shall continue until the Expiration Date, if any. Notwithstanding the foregoing, Zimmermann may terminate this Agreement immediately if you fail to comply with any of the limitations or other requirements in this Agreement. Upon any termination or expiration of this Agreement, you must immediately cease use of the Software and the Documentation and destroy all copies of the Software and Documentation.

It may not even matter. The installer package (for version 0.0.1 build 27 on OS X) doesn't have the license agreement - it's the website with the download link that does.

Meanwhile, is the name zFone or Zfone? It may be trivial, but from a marketing point of view I believe it matters. The application's "zFone" menu doesn't even seem to know (there are two menu items that say "zFone" and two with "Zfone").

ZFone

So is this one Free Software?

(and can you redistribute it once you've provided your email address to Phil for the download link?)

Re:ATTENTION /. MODS: DO NOT MOD THIS DOWN!!!

The jedi mind trick doesn't work too well when it's typed. Try again next time. You are not a winner.

Re:A-Splode

Grumberto? Is that you?

-Peter