atom feed22 messages in org.oasis-open.lists.officeRe: [office] Passwords
FromSent OnAttachments
Patrick DurusauNov 27, 2006 4:51 pm 
David FaureNov 28, 2006 1:07 am 
Daniel CarreraNov 28, 2006 1:40 am.pgp
Florian ReuterNov 28, 2006 2:32 am 
Daniel CarreraNov 28, 2006 2:51 am.pgp
Dave PawsonNov 28, 2006 2:58 am 
Daniel CarreraNov 28, 2006 3:12 am.pgp
Patrick DurusauNov 28, 2006 3:30 am 
Daniel CarreraNov 28, 2006 6:29 am.pgp
Patrick DurusauNov 28, 2006 6:47 am 
Daniel CarreraNov 28, 2006 6:59 am.pgp
robe...@us.ibm.comNov 28, 2006 7:37 am 
Michael Brauer - Sun Germany - ham02 - HamburgNov 28, 2006 7:42 am 
Daniel CarreraNov 28, 2006 8:16 am.pgp
Patrick DurusauNov 28, 2006 11:07 am 
Daniel CarreraNov 29, 2006 1:07 am.pgp
Michael Brauer - Sun Germany - ham02 - HamburgDec 8, 2006 2:50 am 
Daniel CarreraDec 8, 2006 3:54 am.pgp
Michael Brauer - Sun Germany - ham02 - HamburgDec 8, 2006 4:18 am 
Michael Brauer - Sun Germany - ham02 - HamburgJan 15, 2007 2:24 am 
Zhi Yu YueJan 15, 2007 6:19 am 
Michael Brauer - Sun Germany - ham02 - HamburgJan 15, 2007 6:36 am 
Subject:Re: [office] Passwords
From:Daniel Carrera (dani@zmsl.com)
Date:Nov 28, 2006 6:29:02 am
List:org.oasis-open.lists.office
Attachments:
pgp00003.pgp - 0.3k

On Tue, 2006-28-11 at 11:11 +0000, Daniel Carrera wrote:

Yes, that would be good. We can say that SHA1, SHA256, SHA512 and RIPMEND-160 are all ok (list taken from xmlenc), but all implementations must support at least SHA256 but preferably all.

I know this is moving further away from Florian's list, but I think we should also include WHIRLPOOL. There are good reasons for this:

1) SHA and RIPMEND are based on the same design principles, the same as MD4/MD5, and hashes from this family are continuously being broken (MD4, MD5, SHA-0, SHA-1 and the original RIPMEND). Some worry that there is a fundamental design problem (see Bruce Schneier) and we need a completely different algorithm.

WHIRLPOOL is the only popular hash I know of that is of a different design.

2) WHIRLPOOL is an ISO standard (ISO/IEC 10118-3), is un-patented, is believed to be secure, and it has been recommended by the NESSIE project.

NESSIE = New European Schemes for Signatures, Integrity and Encryption

http://en.wikipedia.org/wiki/NESSIE

I notice that NESSIE did _not_ recommend SHA-1 at all, but only the later variants.

In fact, why don't we use the NESSIE list instead of xmlenc? NESSIE's list is WHIRLPOOL, SHA-256, SHA-384 and SHA-512.

I would feel more comfortable using this list than the other one. And we could say that applications must support at least WHIRLPOOL and SHA-256.

What do you think?

Cheers, Daniel.