Jump to content

Talk:Dining cryptographers problem

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Burningstarfour (talk | contribs) at 19:00, 4 May 2011. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

It has been suggested that this page and Dining cryptographers protocol are too closely related and should be merged. There was some progress made in rewriting the article, Dining_cryptographers_protocol/Rewrite, but it hasn't seen any content updates since March 2008. Thoughts? -- Autopilot (talk) 14:59, 7 March 2009 (UTC)[reply]

There are actually 3 pages about the same topic:

The one that contains the least inaccurate stuff is the last one. The other two pages are very inaccurate.

Some remarks:

  • The generalisation of the protocol IS NOT A RING structure. The idea is that each participant should ideally establish a shared secret with every other participant (fully connected graph). In the story, there are only 3 cryptographers, and in this very situation (fully connected graph with 3 nodes), this looks like a ring. It is however not supposed to be a ring in the general case.
  • There are NO ENCRYPTED LINKS. Particiants use a secure channel (which is a theoretical concept) and not an encrypted link (which has to do with cryptography). This especially wrong because the protocol guarantees unconditional (information theoretical) untraceability, and therefore cannot use cryptography (which is based on the assumption that some problems that are hard to compute).
  • All the other stuff (aging cryptographers, and so on), is absolutely unrelated. I have never heard of this, and I wonder who invented all that stuff. (The dining philosophers problem actually exists, but it is completely unrelated.) There is only the dining cryptographers protocol. All these strange derivations do not exist and do not belong here.
  • An external site that is sometimes referenced contains the same inaccurate information, and should be avoided.
  • The last page has the following problems: It is not about computing a multiparty OR ; Chaum does suggest a reservation technique to avoid collisions (using a reservation vector); and he does suggest a technique to detect disruptors.

That's interesting. If it's not about multiparty OR, what do you think it is computing? Using a trap to capture disruptors is a theoretical concept in Chaum'a paper. Does the paper explain how to do it exactly? Some other papers followed up the trap concept. They assumed the DC-net as a ring and proposed more concrete measures to implement the "trap", but DC-net is not a ring. Fh240 (talk) 13:35, 10 April 2009 (UTC)[reply]

Things one could mention:

  • Sender untraceability is achieved through a technique called superposed sending.

(Not sure what that means. It seems only to confuse people. Fh240 (talk) 13:35, 10 April 2009 (UTC))[reply]

  • Receiver untraceability is based on the reliable broadcast assumption.

(That's illogical. In DC-net, the receiver is untraceable because everyone (including the attacker) is the receiver. Fh240 (talk) 13:35, 10 April 2009 (UTC))[reply]

  • Most relevant work on the topic has been done by Chaum, Pfitzmann, Waidner, Golle and Juels.

(It's necessary to explain what the paper are about before adding the references, so that readers can decide how relevant (or irrelevant) they are. Otherwise, it only confuses people. Fh240 (talk) 13:35, 10 April 2009 (UTC))[reply]

—Preceding unsigned comment added by 85.93.206.248 (talk) 16:00, 7 March 2009 (UTC)[reply]


I am the author of the initial remarks, and I believe they are perfectly valid. Here is the list of papers with the paper that are in my opinion the most relevant about the Dining cryptographers protocol. You will find the detail about everything in these papers (Especially the early papers explain the details of the protocol.) :

158.64.77.254 (talk) 12:16, 12 June 2009 (UTC)[reply]

  • Support merge. I'm not an expert here - I don't know much about cryptography - but it looks to me like we have here three articles covering substantially the same subject. Even if there are differences between them, they could all be covered sa part of one article. Robofish (talk) 00:49, 26 November 2009 (UTC)[reply]