Live data from Hacker News

PGPfone (1995)

en.wikipedia.org

1–10 of 25 posts

Re: PGPfone (1995)

#4

If you're looking for encrypted and decentralized VoIP, http://retroshare.sourceforge.net/ is one handy solution (and a lot more).

Jitsi also uses ZRTP for audio and video on the desktop, and there's RedPhone on Android and Silent Eyes (Silent Circle) for both Android and iOS. There are probably a few others, too.

I'm not sure if it can be used with WebRTC clients, or if it's even needed there.

Re: PGPfone (1995)

#5
post #4

If you're looking for encrypted and decentralized VoIP, http://retroshare.sourceforge.net/ is one handy solution (and a lot more).

Jitsi also uses ZRTP for audio and video on the desktop, and there's RedPhone on Android and Silent Eyes (Silent Circle) for both Android and iOS. There are probably a few others, too. I'm not sure if it can be used with WebRTC clients, or if it's even needed there.

it's actually called "Silent Phone"

Re: PGPfone (1995)

#6
post #4

If you're looking for encrypted and decentralized VoIP, http://retroshare.sourceforge.net/ is one handy solution (and a lot more).

Jitsi also uses ZRTP for audio and video on the desktop, and there's RedPhone on Android and Silent Eyes (Silent Circle) for both Android and iOS. There are probably a few others, too. I'm not sure if it can be used with WebRTC clients, or if it's even needed there.

Personally, I'd stay away from anything that is closed-source (as we don't know what's happening inside) and/or centralized (because it's just one more attack vector and totally unnecessary for VoIP).

Re: PGPfone (1995)

#7
post #4

Earlier quoted context omitted.

Jitsi also uses ZRTP for audio and video on the desktop, and there's RedPhone on Android and Silent Eyes (Silent Circle) for both Android and iOS. There are probably a few others, too. I'm not sure if it can be used with WebRTC clients, or if it's even needed there.

Personally, I'd stay away from anything that is closed-source (as we don't know what's happening inside) and/or centralized (because it's just one more attack vector and totally unnecessary for VoIP).

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

Re: PGPfone (1995)

#8

Earlier quoted context omitted.

Personally, I'd stay away from anything that is closed-source (as we don't know what's happening inside) and/or centralized (because it's just one more attack vector and totally unnecessary for VoIP).

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

RetroShare is completely decentralized/p2p/OTR.

EDIT: @JshWright - Not sure I understand your question, but RS does "real-time voice communication" (besides the other things like chat, messaging, file sharing, forums, channels...)

Re: PGPfone (1995)

#9

Earlier quoted context omitted.

Personally, I'd stay away from anything that is closed-source (as we don't know what's happening inside) and/or centralized (because it's just one more attack vector and totally unnecessary for VoIP).

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

That's Retroshare. It's also the only one as far as I know that has P2P "e-mail", too (besides Bitmessage, which is still quite new and unproven).
Post reply on HN