Jump to content

Talk:k-anonymity

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

This is an old revision of this page, as edited by J2kun (talk | contribs) at 16:32, 4 June 2022 (→‎Password hashing is not k-anonymity: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconCryptography: Computer science Start‑class Mid‑importance
WikiProject iconThis article is within the scope of WikiProject Cryptography, a collaborative effort to improve the coverage of Cryptography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StartThis article has been rated as Start-class on Wikipedia's content assessment scale.
MidThis article has been rated as Mid-importance on the importance scale.
Taskforce icon
This article is supported by WikiProject Computer science (assessed as Mid-importance).
WikiProject iconInternet Start‑class Mid‑importance
WikiProject iconThis article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StartThis article has been rated as Start-class on Wikipedia's content assessment scale.
MidThis article has been rated as Mid-importance on the project's importance scale.

Randomization included?

it appears that Kishor has changed gender from Male to Female in the anonymization step. Is the article intended to suggest that k-anonymization also permits explicit falsification of data in order to acheive some k-anonymous property? — Preceding unsigned comment added by Dkgdkg (talkcontribs) 01:50, 22 April 2014 (UTC)[reply]

No, that would be in error and is no longer the case. WilliamKF (talk) 00:49, 22 May 2014 (UTC)[reply]

First introduced 1998 by Samarati/Sweeney?

The introduction states, that the concept of k-anonymity was first introduced in 2002.

However, the paper "Protecting privacy when disclosing information: k-anonymity and its enforcement through generalization and suppression", released in 1998 by Samarati/Sweeney[1] clearly introduces those concepts a few years earlier.

Is my understanding off, or is the information in the article just incomplete? 42ndTowel (talk) 23:16, 28 April 2015 (UTC)[reply]

The information in the article is complete in the sense that it formally develops the definition of k-anonymity. The issue is with the date of publication. A search of IEEE Explore, ACM Digital Library, and DBLP revealed no refereed papers pre-dating the 2002 journal paper. A formal definition based on the journal article will vastly improve the quality of this article. Vonkje (talk) 14:10, 23 July 2015 (UTC)[reply]
I believe the issue is that the earlier paper was a tech report published by SRI [2]. Not being peer reviewed or published by a publishing house, the IEEE, ACM, and DBLP probably don't consider it significant enough to list. However, I believe it would count as a publication for legal purposes such as patents. Thus, I suggest taking the earlier paper as the first. Duckpigcow (talk) 05:54, 14 October 2016 (UTC)[reply]
There also appears to be an abstract from 1998, maybe based on the tech report, in ACM's library [3]. Duckpigcow (talk) 06:02, 14 October 2016 (UTC)[reply]

References

clarify paragraph

This makes no sense to a layman; there is no context and the terminology is not covered by this article:

For example, researchers showed that, given 4 points, the unicity of mobile phone datasets ( E 4 {\displaystyle {\mathcal {E}}_{4}} , k-anonymity when k = 1 {\displaystyle k=1} ) can be as high as 95%. — Preceding unsigned comment added by 100.1.206.144 (talk) 01:44, 9 July 2018 (UTC)[reply]

Password hashing is not k-anonymity

Despite the accurate descriptions of "media coverage", the description of breached password checking as using k-anonymity seems misleading. k-anonymity is meant to keep a database private, but the mechanisms for password checking does not keep the database private at all. It only protects the client's privacy. This should be mentioned in the article.