Jump to content

Talk:Concrete security

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by Jlwoodwa (talk | contribs) at 03:28, 28 April 2024 (untitled). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Untitled

[edit]

Could someone give me some feedback on whether the article in the current form is comprehensible please. Thanks Arvindn 04:49, 23 July 2005 (UTC)[reply]

Arvind, The article looks good but for some minor issues.
The following passage doesn't make it clear to a naive reader about what is an "oracle query". Also, the phrase "number of plaintexts it can see" reads rather unencyclopedic.
Concrete security parametrizes all the resources available to the adversary, such as running time, memory, number of oracle queries, number of plaintexts it can see, etc. (the exact list is problem specific.) Then the advantage of the adversary is upper bounded as a function of these resources and of the problem size. It is often possible to give a lower bound (i.e, an adversarial strategy) matching the upper bound, hence the name exact security.
One other minor issue is the linking of the words "significant" and "advantage" to entirely different articles. Not many would assume that they might lead to these topics. -- Sundar \talk \contribs 13:28, July 29, 2005 (UTC)
Fixed, thanks Arvindn 16:37, 29 July 2005 (UTC)[reply]