vuvuzela / vuvuzela Goto Github PK

View Code? Open in Web Editor NEW

2.5K 151.0 189.0 772 KB

Private messaging system that hides metadata

Home Page: https://vuvuzela.io

License: Other

Go 100.00%

vuvuzela metadata privacy messaging chat cryptography golang research

vuvuzela's Introduction

Metadata absolutely tells you everything about somebody's life

— Stewart Baker, former General Counsel of the NSA

We kill people based on metadata

— Michael Hayden, former Director of the NSA

Vuvuzela

Vuvuzela is a messaging system that protects the privacy of message contents and message metadata. Users communicating through Vuvuzela do not reveal who they are talking to, even in the presence of powerful nation-state adversaries. Our SOSP 2015 paper explains the system, its threat model, performance, limitations, and more. Our SOSP 2015 slides give a more graphical overview of the system.

Vuvuzela is the first system that provides strong metadata privacy while scaling to millions of users. Previous systems that hide metadata using Tor (such as Pond) are prone to traffic analysis attacks. Systems that encrypt metadata using techniques like DC-nets and PIR don't scale beyond thousands of users.

Vuvuzela uses efficient cryptography (NaCl) to hide as much metadata as possible and adds noise to metadata that can't be encrypted efficiently. This approach provides less privacy than encrypting all of the metadata, but it enables Vuvuzela to support millions of users. Nonetheless, Vuvuzela adds enough noise to thwart adversaries like the NSA and guarantees differential privacy for users' metadata.

Screenshots

A conversation in the Vuvuzela client

In practice, the message latency would be around 20s to 40s, depending on security parameters and the number of users connected to the system.

Noise generated by the Vuvuzela servers

Vuvuzela is unable to encrypt two kinds of metadata: the number of idle users (connected users without a conversation partner) and the number of active users (users engaged in a conversation). Without noise, a sophisticated adversary could use this metadata to learn who is talking to who. However, the Vuvuzela servers generate noise that perturbs this metadata so that it is difficult to exploit.

Acknowledgements

This code is written by David Lazar with contributions from Jelle van den Hooff, Nickolai Zeldovich, and Matei Zaharia.

vuvuzela's People

Contributors

Stargazers

Watchers

Forkers

nullren silky darg0001 chdanish spacefoundry neuhaus rdprdprdp debunge gera3dartist shinsec aypak evilrovot andradeandrey kk9599 99plus2 mdlx rajivraj luk3k0 rvaliev kevinmel2000 tml emmanuelfarrar rgaidot jartysiewicz vbraguimcanto user360 bluebear171 justintung allengaller sxhao pirater hkingz overcls gale320 maoyikun snowman2074 kknet sayi21cn eastlhu rivenx williamren mobilefzb yourchanges codevlabs read-later datachand rasata duzhanyuan luan-cestari zqqq bibekmahrzn matejlach mediaeater pojoba02 gombadi tartaruszen kangkot liufeiit sohailalam2 kissthink daodaoliang rockylo cngolang paulnew fengzi2023 sumyfly samolee fhernandez173 icloudkit freejavaster jsonmess chrisemoulton chr0nu5 xin2893 grasswin jiexiajoy jothatron carlosmoran092 eqyun jorycn waiducom baeeq cswang mgraham134 andy737 xr00x vonnordmann geasscode di-stars yanglangfei leetec rainbowforce thomasmodeneis cvaldemar panenming yuanfeng0905 miffa levinlin jhayes14 hotelzululima

vuvuzela's Issues

How does this compare to Dissent?

http://dedis.cs.yale.edu/dissent/

Scrolling support

A user should be able to scroll up/down in a windows message history to read past discussion.

I think that Page Up/Page Down is sufficient, similar to how irssi behaves.

Registration Tokens ... metadata leak?

This may show a naive understanding of your work. So please forgive me if it is a silly question and a non-issue.

I was just curious about the necessity of acquiring a registration token...Surely the server providing this token can trivially link IP addresses with vuvuzela usernames?

LICENSE should actually be the GPLv3

I don't understand why it is a stub?

Redo analysis for multiple conversations

The Vuvuzela client now supports 5 concurrent conversations. We were thinking this gives you 1/5th the privacy budget, but it's likely worse than that.

rand/cpu_amd64.s error: "no such instruction: `text ·cpu(SB),NOSPLIT,$0-8'"

$ go get github.com/davidlazar/vuvuzela/...
# github.com/davidlazar/go-crypto/encoding/base32
ar: `u' modifier ignored since `D' is the default (see `U')
# golang.org/x/crypto/poly1305
ar: `u' modifier ignored since `D' is the default (see `U')
# golang.org/x/crypto/salsa20/salsa
ar: `u' modifier ignored since `D' is the default (see `U')
# golang.org/x/crypto/curve25519
ar: `u' modifier ignored since `D' is the default (see `U')
# golang.org/x/crypto/salsa20
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/davidlazar/vuvuzela/vrpc
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/Sirupsen/logrus
ar: `u' modifier ignored since `D' is the default (see `U')
# golang.org/x/crypto/nacl/secretbox
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/davidlazar/vuvuzela/internal/box
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/davidlazar/vuvuzela/rand
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s: Assembler messages:
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:4: Error: no such instruction: `text ·cpu(SB),NOSPLIT,$0-8'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:5: Error: bad expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:5: Error: junk `version information' after expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:6: Error: bad expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:6: Error: junk `any leaf will do' after expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:7: Error: bad expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:7: Error: junk `any subleaf will do' after expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:10: Error: no such instruction: `byte $0x0f'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:11: Error: no such instruction: `byte $0xa2'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:13: Error: bad expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:13: Error: junk `logical cpu id is put in EBX[31-24]' after expression
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:14: Error: too many memory references for `movq'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:5: Error: invalid operands (*UND* and *ABS* sections) for `/'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:5: Error: division by zero
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:6: Error: invalid operands (*UND* and *ABS* sections) for `/'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:6: Error: division by zero
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:7: Error: invalid operands (*UND* and *ABS* sections) for `/'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:7: Error: division by zero
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:13: Error: invalid operands (*UND* and *ABS* sections) for `/'
go/src/github.com/davidlazar/vuvuzela/rand/cpu_amd64.s:13: Error: division by zero
# golang.org/x/crypto/nacl/box
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/davidlazar/vuvuzela/internal
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/mattn/go-runewidth
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/gorilla/websocket
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/nsf/termbox-go
ar: `u' modifier ignored since `D' is the default (see `U')
# github.com/jroimartin/gocui
ar: `u' modifier ignored since `D' is the default (see `U')
# gopkg.in/gizak/termui.v1
ar: `u' modifier ignored since `D' is the default (see `U')

$ rpm -q gcc-go
gcc-go-5.3.1-2.fc23.x86_64

Servers do not restart gracefully

Install Issue

$ go get github.com/davidlazar/vuvuzela/...

package golang.org/x/crypto/salsa20: unrecognized import path "golang.org/x/crypto/salsa20"
package golang.org/x/crypto/nacl/box: unrecognized import path "golang.org/x/crypto/nacl/box"

Decentralized / Distributed Vuvuzela

Ideally, anyone could contribute a small Vuvuzela server, similar to how Tor works.

Re-registration of an email address

I created an account on the site and received a token, but did not /register during the delay (24 hours). Now I can not /register (it's too late) nor re-create the account using this very same address. If the address dead, or is there a way to receive a new token for it?

Dummy dialing dead drop is not noised

This means an attacker can see how many users didn't dial in a given round, and thus knows how many users did dial (even though the other dialing dead drops are noised).

panic: invalid argument

I just reserved a username on the homepage and after a couple of tries I managed to successfully install vuvuzela-client on Ubuntu Xenial with go version go1.9.2 linux/amd64. Unfortunately, every time I try to register my username, the login fails:


user@hostname:~$ vuvuzela-client -username user
panic: invalid argument

goroutine 1 [running]:
main.(*GuiClient).Run(0xc42023a400, 0xc420230000)
        /home/user/go/src/vuvuzela.io/vuvuzela/cmd/vuvuzela-client/gui.go:1076 +0x7b7
main.main()
        /home/user/go/src/vuvuzela.io/vuvuzela/cmd/vuvuzela-client/main.go:54 +0x394

UPDATE1
I did the same procedure of installing the client on a Debian Stretch 64-bit VM and it works immediately. What is the issue on Ubuntu? The go version on the Debian VM: go version go1.8.1 linux/amd64

connection error since May 16

i have updated app "go get -u vuvuzela.io/vuvuzela/cmd/vuvuzela-client" but it does not help

-!- Connection error: inconsistent PKG status for "randy":
· PKG pkg1.vuvuzela.io:8443: OK
· PKG nickolai.srv.vuvuzela.io:54331: Post https://nickolai.srv.vuvuzela.io:
54331/status: dial tcp 50.202.194.198:54331: connect: connection refused
· PKG pkg2.vuvuzela.io:8443: OK
-!- Type /connect after resolving the issue to try again.

Dialing noise is distinguishable

The FillWithFakeIntroductions function generates encrypted introductions by filling an array with random bytes. However, a legitimate encrypted introduction contains a box public key, which is distinguishable from random.

Forward secrecy for message contents

Implement some sort of ratcheting.

/w 0 -> panic

I typed "/w 0" to get back to the main screen, but got a panic instead. Oops.

Port Karaoke's optimistic indistinguishability to Vuvuzela

We can make Vuvuzela immune to passive traffic analysis by implementing Karaoke's optimistic indistinguishability. This mostly involves changing the Vuvuzela client to send 2 messages in every round and to do something reasonable when messages are dropped.

https://davidlazar.org/papers/karaoke.pdf

Implement backoff in coordinator

The coordinator should not continue to start new rounds if there are too many outstanding rounds.

cant install vuvuzela

Xubuntru 17.10:
go get -u vuvuzela.io/vuvuzela/cmd/vuvuzela-client
gives me
"# vuvuzela.io/crypto/bn256
exec: "gcc": executable file not found in $PATH"

Windows-10:
go get -u vuvuzela.io/vuvuzela/cmd/vuvuzela-client
gives me
"# vuvuzela.io/crypto/bn256
exec: "gcc": executable file not found in $PATH"

Debian 9:
"# vuvuzela.io/crypto/bn256
exec: "gcc": executable file not found in $PATH"

How to use usernames instead of e-mail addresses

So these past months I didn't have the possibility to pursue my interest in vuvuzela due to reasons. Now I want to return to vuvuzela and notice that it registers usernames as actual e-mail addresses. At first, I thought that this is optional for those who can't keep a tidy environment for their data, but I don't see any possibility now to use the original usernames. This is very unfortunate for people like me, because I can keep my data environment tidy and I don't see any purpose in using an actual e-mail address to register my token. In fact, it is a huge counter argument for me to keep using this program if I actually have to register using a valid e-mail address. The whole anonymity point gets kind of wonky, as well. Especially considering, that vuvuzela is revolutionary in regards to protecting metadata while e-mails are as clear as a drinking glass. Even with protected e-mail services, the metadata is easily discoverable.
It gets even more weird, since one such untidy person can still lose access to their e-mail, so the whole recovery point becomes futile.

Did I misunderstand something and I can use my original username or do I really have to register using a valid e-mail address now?

 -!- Connection error: inconsistent PKG status for "user":
  ·  PKG pkg1.vuvuzela.io:8443: invalid username: username must be a valid email address: user
  ·  PKG nickolai.srv.vuvuzela.io:54331: invalid username: username must be a valid email address: user
  ·  PKG pkg2.vuvuzela.io:8443: invalid username: username must be a valid email address: user
 -!- Type /connect after resolving the issue to try again.

[Feature] Add Chatroom Support

Feature: Add support for public chatrooms.

Reduce dialing bandwidth

Client retransmission protocol

The client should implement a protocol to ensure messages are delivered.

Indicate status of sent messages

There's 4 possible statuses for sent messages:

Picked up at the server (because we got another message in exchange)
Not picked up by our peer (because we got our own message back)
Not sent yet
Didn't get any response back (network outage?)

We could color your username in each sent message differently depending on its status.

Windows binary

Dear @davidlazar,
Could you be so kind to generate .exe for the rest of us who are mere Windows users w/o compiler?

Switch back to email addresses as usernames

Currently, with usernames, there isn't a good recovery mechanism for users that lose their keys. Originally we were thinking to let a user reset their account if they haven't extracted a key in 30 days (with no further verification), but this would lead to users losing their usernames if they go offline for an extended period.

With email addresses, we could at least verify that the user owns their email address before resetting the account. This would mean that users don't have to worry as much about losing their username, even if they go offline for a long time.

This is technically an issue with Alpenhorn, but I'm posting it here for wider visibility.

[Documentation] Vuvuzela vs Ricochet

Is there any in depth analysis of the pros/cons of using Vuvuzela over Ricochet?

Integrate PKI

Consider using Keytree or Keybase as Vuvuzela's PKI.

[Question] The reason for operating in rounds

Hi, this is not an issue but a question about the approach. In trying to read and understand the Vuvuzela research paper, I couldn't find the reason for why it operates in rounds. Is this a requirement for differential privacy? If there is prior work that helps explain this, could you point me towards that. Thanks.

Change license to AGPLv3+

The GNU Affero General Public License is recommended by the FSF for any software that will commonly be run over a network.

https://en.wikipedia.org/wiki/Affero_General_Public_License

cant register email

After clicking a button I get message:

There were errors creating your account:
error sending email: missing port in address
error sending email: missing port in address
error sending email: missing port in address

inconsistent PKG status

I've successfully created account via vuvuzela.io.
Updated vuvuzela client.
But after start got error message "inconsistent PKG status".

It's possible to /addfriend your own username

Forward secrecy for message metadata

Transfer repo to the new organization

https://github.com/vuvuzela

cmd/vuvuzela-client: add command to delete sent friend requests

I have sent friend request to non-existant user (I suppose). Now I see this request after "/list" command but I can't delete it. Maybe it should just expire in NN days?

Group conversations

Failed to generate Alpenhorn client

After registering with an email address on the site and receiving a token, I proceeded to run the client:

[2019-02-05 ☱ 13:19 ☴  ~]$ vuvuzela-client -username [email protected]
Failed to generate new Alpenhorn client: fetching latest dialing config: config expired on 2019-02-02 09:01:48.838394379 -0500 EST

go version go1.11.5 darwin/amd64
echo $GOPATH=/Users/myusername/go

Client should measure latency to the coordinator

The client should take into account the latency to the coordinator when deciding when to send its onion for a round.

debugfriend %!q(MISSING)

I tried to do a /debugfriend and got this:

 -!- %!q(MISSING) is not in your friends list!

If two users /addfriend eachother, and one /approves, there's an outstanding request that cannot be removed.

Command aliases

/win should be an alias for /w
/talk should be an alias for /call

Allow changing windows by /w <number> or /win <number>

It would be nice if I could switch windows the same way I do in irssi.

Reduce noise by rotating servers

CDN for dialing dead drops

incomplete extraction

excellent work...!

there are some issues ( maybe and not related to TOR, if connecting (tunneling vuvuzela traffic) through TOR in order to reach the server )
Welcome to Vuvuzela. Type /help for help.
-!- Connected to AddFriend service!
-!- Connected to Dialing service!
-!- Connected to Convo service!
-!- 22:55:26 ! sendAddFriendOnion: incomplete extraction for round 219404
-!- 22:55:35 ! scanMailbox: incomplete extraction for round 219404
-!- 22:57:47 ! sendAddFriendOnion: incomplete extraction for round 219414
-!- 22:57:57 ! scanMailbox: incomplete extraction for round 219414
-!- 22:58:01 ! sendAddFriendOnion: incomplete extraction for round 219415
-!- Disconnected from AddFriend service: websocket: close 1006 (abnormal closure): unexpected EOF (reconnecting in 10s)
-!- Disconnected from Dialing service: websocket: close 1006 (abnormal closure): unexpected EOF (reconnecting in 10s)
-!- Disconnected from Convo service: websocket: close 1006 (abnormal closure): unexpected EOF (reconnecting in 10s)
-!- 22:58:22 ! write tcp 10.138.3.2:34582->128.52.176.149:8443: i/o timeout call=WriteJSON
-!- 22:58:29 ! scanMailbox: incomplete extraction for round 219415
-!- Connected to AddFriend service!
-!- Connected to Convo service!
-!- Connected to Dialing service!
-!- 23:01:52 ! error from dialing coordinator: wrong round (want 473737) round=473736
-!- 23:01:52 ! sendAddFriendOnion: incomplete extraction for round 219431
-!- 23:02:02 ! scanMailbox: incomplete extraction for round 219431
-!- 23:06:24 ! error from dialing coordinator: wrong round (want 473781) round=473780
-!- 23:06:26 ! error from dialing coordinator: wrong round (want 473782) round=473781
-!- 23:06:33 ! sendAddFriendOnion: incomplete extraction for round 219451
-!- 23:06:42 ! scanMailbox: incomplete extraction for round 219451
-!- 23:06:59 ! sendAddFriendOnion: incomplete extraction for round 219453
-!- 23:07:08 ! scanMailbox: incomplete extraction for round 219453

.... what's going on......thanks in advance !!

So how does this compare with WASTE?

Having been around the web for a while, I'm familiar with Justin Frankel's last stand at Nullsoft, WASTE.
https://en.wikipedia.org/wiki/WASTE

It keeps resurfacing over and over...
http://wasteagain.sourceforge.net/

What's different this time?

Line 234 in 2304d37

dummy := new(convo.DeadDropMessage)