Talk:NESSIE

Computer Security: Computing Mid‑importance

This article is within the scope of WikiProject Computer Security, a collaborative effort to improve the coverage of computer security 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.Computer SecurityWikipedia:WikiProject Computer SecurityTemplate:WikiProject Computer SecurityComputer Security articles

Mid

This article has been rated as Mid-importance on the project's importance scale.

This article is supported by WikiProject Computing (assessed as Mid-importance).

Things you can help WikiProject Computer Security with:

Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...

Review importance and quality of existing articles
Identify categories related to Computer Security
Tag related articles
Identify articles for creation (see also: Article requests)
Identify articles for improvement
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
Find editors who have shown interest in this subject and ask them to take a look here.

Cryptography: Computer science Mid‑importance

	This 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.CryptographyWikipedia:WikiProject CryptographyTemplate:WikiProject CryptographyCryptography articles
Mid	This article has been rated as Mid-importance on the importance scale.
	This article is supported by WikiProject Computer science (assessed as Mid-importance).

'Public domain' ambiguity

Ciphergoth,

The term public domain is probably best known from copyright discussions, but it applies to intellectual property more generally. When the patent on an invention expires, it becomes available for use by anyone, and the (no longer enforceable) patent is now held 'in the public domain'. Accordingly, your effort in rewording to avoid the phrase, while admirable, was more work than was required. I'll come back (if I remember) to reinstate it after a period for comment -- from you or anyone else. ww 17:56, 15 February 2006 (UTC)[reply]

I agree that the term "public domain" is in respect to both patent and copyright (from public domain: "If an item is not in the public domain, this may be the result of a proprietary interest as represented by a copyright or patent"). However, there's the possibility of confusion when it comes to describing a cipher as in public domain, namely, are we saying the cipher is patented, or are we saying that an implementation has been released into the public domain (in the copyright sense)? I think many people could assume the latter, and Ciphergoth's new wording makes it clear what exactly is being said. — Matt Crypto 18:01, 15 February 2006 (UTC)[reply]

I think there's a fundamental misunderstanding here. If I patent crypto algorithm FOO, I have an enforcable right to exclusive use of it -- in any form whatsoever -- wherever the patent runs. RSA was not patented outside the US, for technical timing reasons having to do with patent office rules, but was patented within the US. So pgpi.com could post and distribute PGP containing RSA without trouble. It could not post and distribute RSADSI's source code of RSA without permission as it was covered by copright upon creation. But no implementation, regardless of copyright status (I wrote one in 1980, so I owned the copyright in it) could be used in the US as long as the patnet continued in force, lest RSA sue. And win. That this sort of reasoning is twisty twisty is no impediment tot the legal beagles and the courts, so perforce we must deal, there being no choice.

So you and Ciphergoth could exchange successive versions of some implementation of FOO, and one or both would likely own the copyright, and you could even publish the final version somewhere and license it under the GPL or even put it into the public domain. As long my patent is not in the public domain, you can't use it, lest I sue, and win. If I put the patent into the public domain (as RSADSI did for RSA in the last month or so) you free to do as you wish and build your implementation into whatever you'd like. But only then. ww 08:44, 16 February 2006 (UTC)[reply]

Yes, but since "public domain" can refer to either the patent status of the algorithm or the copyright status of some implementation (or both), when we label an algorithm as "public domain" it may not be clear which we're referring to. Hence Ciphergoth's change to make explicit that we're discussing patents clears up that possible confusion. — Matt Crypto 16:57, 16 February 2006 (UTC)[reply]

agreed. ww 17:12, 18 February 2006 (UTC)[reply]

Merger proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

The result of the discussion was no consensus to merge. As I read it, this discussion is roughly evenly divided between opposers and supporters of the merge. I see no reason to believe that this will resolve itself by extending the discussion. Quasi human | Talk 11:33, 12 February 2012 (UTC)[reply]

Following a discussion in Talk:Q (cipher), we propose that merely being part of a competition that allows any entrant isn't a mark of sufficient notability to have an article, and so those ciphers that never made it past the first round of these contests and have no other claim to notability should be merged into this article. I think that's Q (cipher), Nimbus (cipher), NUSH, Grand Cru (cipher), Hierocrypt, LILI-128. ciphergoth (talk) 12:51, 18 January 2009 (UTC)[reply]

I'm not sure about Hierocrypt, since those ciphers were actually adopted as Japanese standards through CRYPTREC, giving them more notability. Ntsimp (talk) 15:28, 18 January 2009 (UTC)[reply]

Yes, that's enough to save it. Thanks! ciphergoth (talk) 09:11, 19 January 2009 (UTC)[reply]

I don't care much about how the articles are structured (one big or several small) but even ciphers like Q have reliable sources published about them, enough to sustain an article. So I would only support merging if the coverage of the ciphers isn't cut down. Mango juice^talk 15:04, 3 March 2009 (UTC)[reply]

Have anyone Grand Cru source code (implementation)? It's great cipher, I think it must have an article, not only as part of NESSIE. --Alexanderwdark (talk) 09:32, 29 March 2009 (UTC)[reply]

I don't think your liking of it is enough to justify an article by itself :-) what is it you like about it? ciphergoth (talk) 11:22, 30 March 2009 (UTC)[reply]

Rather than combine with NESSIE, consider... NESSIE was a competition and so discussion about the history and selection "process" makes sense there. Indeed, the NESSIE article should identify all the submissions and dispositions, but the NESSIE article is not the proper place for a general discussion comparing and contrasting algorithm architectures. To do so would leave out algorithms not submitted to NESSIE, and an incomplete architectural discussion would result. Leave Grand Chu as an individual article, or perhaps combine it with an article discussing the strengths and weaknesses of all block ciphers, including those that were never part of the NESSIE process. That would make more sense to me. --Larry —Preceding unsigned comment added by 76.104.201.22 (talk) 07:38, 10 August 2010 (UTC)[reply]

I agree. Even if these ciphers technically don't pass WP:N, I'd say we invoke WP:IGNORE here, until someone actually proposes them for deletion or something. -- intgr [talk] 15:33, 29 August 2010 (UTC)[reply]

Also agree. It makes no sense to have the NESSIE article covering the selected algorithms with just a few words (link and submittor) and the non-selected algorythms in great detail. --Danh (talk) 12:57, 20 September 2010 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.