Re: [saag] Algorithms/modes requested by users/customers

"Vishwas Manral" <vishwas.ietf@gmail.com> Fri, 22 February 2008 00:59 UTC

Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.13.6/8.12.8) with ESMTP id m1M0xAgt017851 for <saag@PCH.mit.edu>; Thu, 21 Feb 2008 19:59:10 -0500
Received: from mit.edu (W92-130-BARRACUDA-2.MIT.EDU [18.7.21.223]) by fort-point-station.mit.edu (8.13.6/8.9.2) with ESMTP id m1M0x2Z1029949 for <saag@mit.edu>; Thu, 21 Feb 2008 19:59:03 -0500 (EST)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mit.edu (Spam Firewall) with ESMTP id 48B17CD653B for <saag@mit.edu>; Thu, 21 Feb 2008 19:59:02 -0500 (EST)
Received: by ug-out-1314.google.com with SMTP id e2so1045125ugf.36 for <saag@mit.edu>; Thu, 21 Feb 2008 16:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=+ZV8f3svxlezc2j2UlWrCZMKiARSUo9TJxrfDtlpRF8=; b=wmyhVV/koZt7I6VzX7bR73mAWkje9gVW42jnIX9ygvTWTqodywhGodls7Z1BOwZftLzv+AoeCQXq+p9oTOlQzSii4bLSURYG2ih+cfmAnU/PqURx9oLUI24+CDxar/eLRZQdvUPC6KwVW/r3bqK+foEUpwBHoufUxosUDp4wb8Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PEm/8Jp8PP+iw3048gdZTg3mxNd0uRU9n7vjh5rY0KWqw6gfYI1JCbhU3+IHtXTx2LSA597aYua5NzSiMLL6Y2veBAVXJK4VYFEWfGYlwWwIFj9ETHQ3Oz4Ymaogolrn+ZV6NhqXPHZ2E5QZA4RDdnqZKiPyyRd77P9PEhaWiNw=
Received: by 10.142.100.1 with SMTP id x1mr8247112wfb.131.1203641940205; Thu, 21 Feb 2008 16:59:00 -0800 (PST)
Received: by 10.143.164.14 with HTTP; Thu, 21 Feb 2008 16:59:00 -0800 (PST)
Message-ID: <77ead0ec0802211659led5fe3axb7c8a1a27e190c1@mail.gmail.com>
Date: Thu, 21 Feb 2008 16:59:00 -0800
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Jon Callas <jon@callas.org>
In-Reply-To: <57147A59-BFAE-4F55-AE28-C653EB7475D1@callas.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <p06240804c3de211f0592@10.20.30.162> <p06240804c3e0ad5d1fa4@10.20.30.152> <FAD1CF17F2A45B43ADE04E140BA83D483C4E93@scygexch1.cygnacom.com> <p06240806c3e0c794447c@10.20.30.152> <FAD1CF17F2A45B43ADE04E140BA83D483C4E9D@scygexch1.cygnacom.com> <p06240809c3e0d3f52b5b@10.20.30.152> <57147A59-BFAE-4F55-AE28-C653EB7475D1@callas.org>
X-Spam-Score: 0.12
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Cc: saag@mit.edu
Subject: Re: [saag] Algorithms/modes requested by users/customers
X-BeenThere: saag@mit.edu
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: IETF Security Area Advisory Group <saag.mit.edu>
List-Unsubscribe: <http://mailman.mit.edu/mailman/listinfo/saag>, <mailto:saag-request@mit.edu?subject=unsubscribe>
List-Archive: <http://mailman.mit.edu/pipermail/saag>
List-Post: <mailto:saag@mit.edu>
List-Help: <mailto:saag-request@mit.edu?subject=help>
List-Subscribe: <http://mailman.mit.edu/mailman/listinfo/saag>, <mailto:saag-request@mit.edu?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2008 00:59:10 -0000

Hi Jon,

>  When PGP first went through FIPS 140, we assigned a dedicated engineer
>  to the process. Shepherding software through FIPS 140 was so painful,
>  so mind-numbing, so annoying that he quit the company, quit
>  cryptography, and quit computer security altogether. He took a job
>  with a company that produced MP3 music software. That company was
>  bought out by Apple, and the software turned into what we now know as
>  iTunes. He is at Apple to this day as the lead of iTunes.
>
>  So the next time you listen to an iPod, think about FIPS 140, and
>  thank the horrible process.
Mind you, iTunes has its own DRM mechanism and that requires
cryptography. I have in the past worked on DTCP-IP which is now the
content protection mechanism in home devices (after DLNA adopted it)
used for content. It uses mechanisms similar to IKE (called AKE) and
DTCP (like IPsec).

So may be it is not as far away from cryptography as you might assume.

Thanks,
Vishwas

>         Jon
>
>
>  -----BEGIN PGP SIGNATURE-----
>  Version: PGP Universal 2.6.3
>  Charset: US-ASCII
>
>  wj8DBQFHu2/hsTedWZOD3gYRAuZbAJ9IFEWuafL6fAB+2MxJvwIEOmLJiACgkJrs
>  eRur6xWa+w6FdH022GobtDg=
>  =ZTOd
>  -----END PGP SIGNATURE-----
>
>
> _______________________________________________
>  saag mailing list
>  saag@mit.edu
>  http://mailman.mit.edu/mailman/listinfo/saag
>