{"action":"created","issue":{"url":"https://api.github.com/repos/irungentoo/toxcore/issues/1552","repository_url":"https://api.github.com/repos/irungentoo/toxcore","labels_url":"https://api.github.com/repos/irungentoo/toxcore/issues/1552/labels{/name}","comments_url":"https://api.github.com/repos/irungentoo/toxcore/issues/1552/comments","events_url":"https://api.github.com/repos/irungentoo/toxcore/issues/1552/events","html_url":"https://github.com/irungentoo/toxcore/issues/1552","id":143669031,"number":1552,"title":"feature request: deniable aliases","user":{"login":"ghostlands","id":10010304,"avatar_url":"https://avatars.githubusercontent.com/u/10010304?v=3","gravatar_id":"","url":"https://api.github.com/users/ghostlands","html_url":"https://github.com/ghostlands","followers_url":"https://api.github.com/users/ghostlands/followers","following_url":"https://api.github.com/users/ghostlands/following{/other_user}","gists_url":"https://api.github.com/users/ghostlands/gists{/gist_id}","starred_url":"https://api.github.com/users/ghostlands/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ghostlands/subscriptions","organizations_url":"https://api.github.com/users/ghostlands/orgs","repos_url":"https://api.github.com/users/ghostlands/repos","events_url":"https://api.github.com/users/ghostlands/events{/privacy}","received_events_url":"https://api.github.com/users/ghostlands/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/irungentoo/toxcore/labels/Feature_Enhancement","name":"Feature_Enhancement","color":"0052cc"},{"url":"https://api.github.com/repos/irungentoo/toxcore/labels/idea","name":"idea","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-03-26T06:10:03Z","updated_at":"2016-04-23T02:41:40Z","closed_at":null,"body":"Just to be clear, the idea being to have one identity with several addresses that cannot be proven to derive from one another.\r\n\r\nThe why is that it takes a lot of bandwidth currently to keep several clients open all the time when the purpose is to be available via several identities. Without any kind of offline messages (just to be clear, I'm not asking for such), keeping in touch via more than one identity is an intensive, expensive, and manual task.\r\n\r\nApologies if this suggestion would take just as much bandwidth but in a different way. Putting the idea out there in case this isn't necessarily so."},"comment":{"url":"https://api.github.com/repos/irungentoo/toxcore/issues/comments/213653863","html_url":"https://github.com/irungentoo/toxcore/issues/1552#issuecomment-213653863","issue_url":"https://api.github.com/repos/irungentoo/toxcore/issues/1552","id":213653863,"user":{"login":"ghostlands","id":10010304,"avatar_url":"https://avatars.githubusercontent.com/u/10010304?v=3","gravatar_id":"","url":"https://api.github.com/users/ghostlands","html_url":"https://github.com/ghostlands","followers_url":"https://api.github.com/users/ghostlands/followers","following_url":"https://api.github.com/users/ghostlands/following{/other_user}","gists_url":"https://api.github.com/users/ghostlands/gists{/gist_id}","starred_url":"https://api.github.com/users/ghostlands/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ghostlands/subscriptions","organizations_url":"https://api.github.com/users/ghostlands/orgs","repos_url":"https://api.github.com/users/ghostlands/repos","events_url":"https://api.github.com/users/ghostlands/events{/privacy}","received_events_url":"https://api.github.com/users/ghostlands/received_events","type":"User","site_admin":false},"created_at":"2016-04-23T02:41:40Z","updated_at":"2016-04-23T02:41:40Z","body":"I may be at my current limit for helping, but here are my current best responses anyway:\r\n\r\n> How to answer from a deniable alias, while still being findable?\r\n\r\n> how do you find your contact?\r\n\r\nReading your whole entry, I think we might be thinking different things re: deniability. I only want it to be impossible to determine mathematically if addresses are derived from the same seed. Methods to correlate them using other methods such as timing and other network activity are later contingencies outside the scope of my bug as intended. Basically unless I'm misunderstanding you, I don't really get the question, because aliases in my thinking should be deployed and responded to/with no differently than normal current addresses; the only difference being they could all be online in the same client at the same time.\r\n\r\n> How do you maintain an ability to deny the existence/use of that alias while still being able to prove that it only could have come from you?\r\n\r\nThis is the part where I think we might be thinking different things about the word \"deniable\". Whoever you exchange that alias address with should be able to trust it every bit as well as any address that is the current norm. They just shouldn't be able to see that it has any relation to any other alias you have out there, should they somehow gather a range of addresses for comparison.\r\n\r\nNo harshness on your part assumed by me. These are technical issues and careful planning and grasp are required.\r\n\r\nOne additional thought that is just outside my scope, but seems important, is beyond the timing correlation problem. Currently, without Tor as a proxy, are the user's IPs transparent? If so, correlation between aliases would happen first there, and the whole thing would be useless (except as a spam deterrent, which Tox already has a solution for)."}}