Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by krbdev.mit.edu (8.9.3) with ESMTP id WAA20887; Mon, 17 Feb 2003 22:11:29 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id WAA02562 for ; Mon, 17 Feb 2003 22:11:28 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id WAA21978; Mon, 17 Feb 2003 22:11:27 -0500 (EST) Received: from all-in-one.mit.edu (ALL-IN-ONE.MIT.EDU [18.18.1.71]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id WAA27951; Mon, 17 Feb 2003 22:11:27 -0500 (EST) Received: (from raeburn@localhost) by all-in-one.mit.edu (8.9.3) id WAA09035; Mon, 17 Feb 2003 22:11:27 -0500 To: krb5-bugs@MIT.EDU Subject: des3 string-to-key From: Ken Raeburn Date: Mon, 17 Feb 2003 22:11:26 -0500 Message-Id: Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-RT-Original-Encoding: us-ascii Content-Length: 558 Our current string-to-key for des3 makes no checks or corrections for weak keys. However, the key schedule generation code will return an error (after generating key schedules, but the error code *is* checked) if any of the three keys is weak. One of the two needs to be changed. The current crypto draft says we don't do weak-key checks, but that's because I looked at our string-to-key and not the key scheduling code. Heimdal does do weak key checking and correction. I'm going to suggest on the WG list that doing the check is the correct fix. Ken