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 at mit.edu > http://mailman.mit.edu/mailman/listinfo/saag >
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.