VOIP Tappings Under Scrutiny
dynooomite writes "CNN.com is reporting that Privacy groups have asked an appellate court to overturn an FCC rule that allows for phone-taps on VOIP calls. The privacy groups made their case saying taps would seriously hinder innovation on the web."
If I choose to encrypt my VOIP traffic using some sort of TLS, would such a ruling allow the FCC to force me to give them my encryption key?
Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
Ohoh... we're (a campus) actually looking at rolling out an inhouse VOIP solution to save us money over the pots system.
The new policy is " for every network drop, put in a phone line" (so cat-5 and cat-3 ran to every wall box) and "for every phone line ran, run a network drop". (same) And this is now (increased) to , two cat-5's and one cat-3 per box.
The thing is, we have so much internal bandwidth that there's no sense paying for the phones they way we are. I mean, for the price of three phone lines per month I can drop a fresh multimode fiber into a core switch. (One time cost!).
We'll see how it goes. I'm hoping for the VoIP solution, since we'll be able to be a lot more flexible and move people and numbers around a lot more. Not to mention all the crap we'll get out of the pipes.
Best,
-=fshalor
Well, I'm just guessing, perhaps they don't mean to physically re-wire the networks but completely change the data flow.
For example, it's highly probable that for privacy concerns they specifically set everything up so nobody in the home office can listen in on any calls. It makes sense, as in case of a security audit they can say "we don't have the ability to eavesdrop, check our infrastructure if you doubt us."
With this ruling they may have to allow feds access to a hub or something that will allow them to intercept all traffic and listen in on both sides. Skype would be a real pain in the but as they supposedly encrypt their transmissions. They'd need access to everyone's keys.
But I'm just guessing here.
Well, if they had any fucking sense, they'd realise it wasn't possible. You can still (In the SIP/SDP case) send an arbitrary codec description over a call. The actual call is point-to-point.
Even taking into consideration the possibility of codec recognition and denying calls based on a restricted set of codecs, you could just place a "signature signal" at the start of the call - something relatively inaudible to the human ear - that triggers encryption etc. Maybe in the same way as Amateur Radioers have a blip at the start/end of speech.
if you encrypt your traffic and the FCC or some other Govt agency attempts/succeeds in breaking your encryption, could it ("they") be found guilty under the DMCA?
"I'm just here to regulate funkiness."
Aside from being a dupe, this submission is worded horribly. The FCC ruling does not allow VOIP-tapping; that's already allowed under standard warrant laws. The ruling is that VOIP providers should be required to make it just as easy to tap a VOIP call as it is to tap a land or cell call, by hooking into the phone company trunk. Given the wandering nature of internet packets, it would be intrusive, expensive, and possibly infeasible to add to an existing system.
Use open source secure VOIP software, preferably developed outside the US. If it doesn't go through a service provider, and it's encrypted, they won't succeed in tapping it without first hacking one of the endpoints, no matter what outrageous laws the FCC takes upon itself to pass.
1.8026175 × 10^12 furlongs per fortnight
c?
Reality has a conservative bias: it conserves mass, energy, momentum...